|
 |
I use MSVC++, and it doesn't complain, so I always forget that they are
their (old habits die very hard). Anyway, I'll get rid of them for the next
release. Sorry about that.
-Nathan
Nieminen Juha <war### [at] punarastas cstutfi> wrote...
> Nathan Kopp <Nat### [at] koppcom> wrote:
> : Writing documentation is so much less fun than writing code. Anyway,
I'll
> : document it soon (it's on my to-do list).
>
> Thanx :)
>
> Btw, I compiled the newest version of uvpov in this Solaris
Sparcstation.
> Your //-comments caused lots of trouble. There's no easy way to
automatically
Post a reply to this message
|
|
|
|
In article <3826f560@news.povray.org> , Nieminen Juha
<war### [at] punarastascstutfi> wrote:
> Btw, I compiled the newest version of uvpov in this Solaris Sparcstation.
> Your //-comments caused lots of trouble. There's no easy way to automatically
> replace them with /* ... */. One problem is that some of the //-comments
> are inside a bigger /**/-comment block, so replacing the //-comments breaks
> the bigger block.
Maybe you should telll your compiler to treat .c files like .cpp files. At
least the official 3.1g source code compiles well using a C++ compiler, and
I suspect the same should work for Nathan's code.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
