Oh,  I thought the comments were messier .. I mean, with the #include file
you'd enter
mass( 1.0)
with the comments it would be
/* mass (1.0) */

Hmm ... maybe I could do BOTH, and have it be an option switch?

Parsing inside comments actually causes problems, what if you are trying to
comment out a mass statement, i.e.

/* this works */
/* mass(1.0) */
/* but let's comment this out */
/* mass (2.0) */
Which one is a real comment?

I realize that the comments were my idea <G>.

Surprised it's just you and me talking about this ...

                  == John ==

"Tim Nikias" <Tim### [at] gmxde> wrote in message
news:3C17DA22.6AAA1898@gmx.de...
> I'd rather go with the comments. They can still be function-style, and
> since you have to read the POV-Script this way or another, I'd think
> it doesn't matter that much which way you choose. But using comments
> would be easier to handle, no #include-files to tamper with...
>
> Tim
>

Post a reply to this message