"Bald Eagle" <cre### [at] netscapenet> wrote:
> "Kenneth" <kdw### [at] gmailcom> wrote:
> 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??
>
> It's not misleading at all.
> You're just not following through with my explanation and seeing what the
> inevitable result is once the parser does the subtraction.
>
> It's now expecting a new scalar value along the spline, and instead, you're
> providing it with a vector value.
>

Yes, I see that-- and the message does make sense...but only *after* the
parser's particular behavior with the negative-index points has been explained
;-) Prior to that, it's a mystery message. And the spline docs are completely
silent about what to expect, unfortunately.

But I agree with several others here, that it's simply better practice to use
commas after every entry-- and to ignore the docs' comma-less example.

Post a reply to this message