"Kenneth" <kdw### [at] gmail com> 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.
- BW
Post a reply to this message
|
