But MegaPov is parsing the macro, just doing a bad job of it.
Like maybe the macro parsing is losing a character somewhere
or something.

Thorsten Froehlich <tho### [at] trfde> wrote in message
news:389640f0@news.povray.org...
> In article <38963bc2@news.povray.org> , "david sharp"
<dsh### [at] interportnet>
> wrote:
>
> > Many macros are being rejected by MegaPov 0.4
> > compiled for DOS (djgpp 2.03, gcc 2.95.2).
> > For example, on parsing
> >
> > /*****************/
> > #macro f(m)
> >         m
> > #end
> >
> > #local d=f(0);
> > /*****************/
> >
> > MegaPov tells me  that it is finding a ';' instead of an expected
> > object or directive (this is with or without a
> >     "#version unofficial MegaPov 0.4"
> > It works fine with the WinMegaPov 0.4 so I am guessing the problem
> > has something to do some difference in compilers or OS.
> > Looking throught the parser code makes me dizzy and I am at a loss
> > trying to find a fix for this.
> > What could it be?
>
> See "A trivial #version conundrum".  This problem is related to FPU
> precision (causing 3.1 to end up as something like 3.099999 but be
compared
> to 3.100000001), search the whole source code for "3.1" and replace it
with
> "3.05", that will fix the problem.

Post a reply to this message