"Bald Eagle" <cre### [at] netscapenet> wrote:
>
> Suddenly, in the untouched MIDDLE of the file, POV-Ray's telling me that I'm
> using > version 3.5 and I need a semicolon.   Great - but it's highlighting a
> line of code that doesn't have anything to do with that (the #end of a for loop
> in the #declare AllStrands union)
>
> So I comment out the vectors declarations, move them to the bottom of the scene
> file, run the scene in 3.8-alpha, 3.71-beta-whatever, 3.7 official, ... same
> thing, only now it's complaining about a perfectly formed #declare identifier =
> value; a few lines down that's worked perfectly for dozens of test renders.
> [though 3.7 official complained about a trailing comma in my sor{} defined by a
> loop]
>
> (#declare Ymax = 0;)
>                   ^ LOOK, you confounded Parser!  There's your precious
> semicolon!
>
> I'm perplexed, confused, and possibly cursed.
>
> It was late, I had a long, sweltering day, and the eyelids were drooping, so I
> decided not to stay up until midnight hunting phantoms.
>
> Perhaps someone else could just run the code to confirm this bizarre behaviour
> and move some lines (at the end near the text block) around to see if the error
> notification changes.  #declare Loc and LA were what I added at the top and then
> moved to the bottom.

Sorry that I can't check into this anymore right now but I did find that same
thing about the sor object getting an error on the Newspline, (comma, no ending
}).
Which is you probably know got a change for the latest versions to allow that.

After removing that comma the memory usage goes "haywire" too, making for a
difficult time forcing a close of POV-Ray 3.7.0. Have not tried 3.8 alpha.

Did see that version message anyhow. Parser sure doesn't like something there!

Post a reply to this message