|
![](/i/fill.gif) |
That's what I was wondering though, unless it was implausible in the
coding of the program then obviously it wouldn't work anyway, but if it
was possible the why not as I said to one of Kens posts:
Simply put, if you had 'light source' instead of 'light_source' and
there was a way the pvengine would only see it when written that way,
ie. *not* when typed in as 'source light' or 'light color' (parser would
say "What the...!? then), I would certainly like that way of things.
A group of words from 2 to ? using spaces, as long as the program code
could discern in the afore-mentioned way, I would think it might be the
best alternative to underscoring.
Mike wrote:
>
> 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.
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/POVring.htm
mailto:inv### [at] aol com?PoV
Post a reply to this message
|
![](/i/fill.gif) |