|
 |
"Bald Eagle" <cre### [at] netscape net> wrote:
> Because the parser has no idea if you're making another point, or subtracting a
> "vector-elevated" scalar value from the preceding vector.
>
> <1, 1, 1> - 0.25 = <1, 1, 1> - <0.25, 0.25, 0.25> = <0.75, 0.75 0.75>
>
> - BW
Hmmm, that does make sense once it's dissected. But should the parser be 'fixed'
somehow, to eliminate this (seemingly) strange behavior? (i.e., unexpected
behavior from a typical user's standpoint?) One problem is with the rather
generic and misleading parse-error statement when the commas are left out:
"Parse error: No matching } , < found instead." Huh??
Post a reply to this message
|
|
