|
 |
I bet there's some side effects that may not be immediately apparent
too. In Keith Rule's Graphic File Formats, he explains why the use of
commas between vector components were added. If you have a vector 1.0 2
0.0, the parser might think you meant <1.02, 0.0, 0>. Something like
that. I bet a lack of underscores could lead to some keywords getting
mixed up.
-Mike
Ron Parker wrote:
>
> On Tue, 23 Feb 1999 12:32:51 -0600, Bob Hughes <inv### [at] aol com> wrote:
> >crss {}
>
> I asked about that one because it's one of the longer new keywords
> in the superpatch. Obviously, it's not one of mine. I don't change
> other people's keywords for compatibility's sake, unless there's a
> conflict (the #macro stuff from the iso patch, for example.)
>
> >Any idea about making spaces available between keywords? Plausible
> >(doable I don't know) to make a keyword recognisable (oops, my Canadian
> >sp.) which goes as a pair of words or more?
>
> Possible but ugly, since the tokenizer splits things on spaces. Even if
> you did make it work with the current tokenizer (and you could, I think)
> you'd get weird error messages if you said something like "max trace 10"
> instead of "max trace level 10" All in all, probably not a good thing.
Post a reply to this message
|
|
