|
From: Daniel J S. <dan...@ie...> - 2004-09-08 22:54:51
|
Daniel J Sebald wrote: > Maybe the following would be too much, but in some sense I'd prefer a > syntax where after the style could be a list of keywords to go along > with that style. These keywords could be aspects unique to that style > and column information unique to that style. (What I'm proposing here > is just a brainstorming sort of thing, not an idea I've had in mind.) > Let me use a hypothetical "points". For example: Of course, there is another aspect of this issue that Petr raised way back, which is the storage of points, i.e., the need for an "x", "y", "xhigh", "yhigh", etc. In some sense, if you know the number of columns, i.e., only v[0], v[1], v[2], have meaning, then only those need be saved. The mapping for the meaning of those columns could be held off. Programming the variable stored point elements wouldn't be too bad, but I guess the advantage for the current set up is that it simplifies the computation for automatic ranging. Dan |