|
![](/i/fill.gif) |
Think you lost me more than I you.
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.
Ken wrote:
>
> Bob Hughes wrote:
> >
> > "Possibly" sounds encouraging.
> > I was thinking along the lines that if the two or more words could be
> > done with spaces then somehow it would be seen *only* when all the group
> > were present, like when part of a keyword is written into the CodeMax
> > editor it shows that the keyword is not all there (also if written
> > wrong) by not switching color. So if all the words were present in
> > proper placement (and spelling) it would be recognized and only then.
>
> I could live with the loss of underscores and abreviated key words
> but have a feeling it would make the language a little too loose
> by adding support for spaces. Personaly I see no advantage to it
> anyway. If you want to do two things to reduce code size and ease
> of entering then turn around and add spaces back in. Where are you
> going with this ?
>
> --
> Ken Tyler
>
> mailto://tylereng@pacbell.net
--
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) |