POV-Ray : Newsgroups : povray.unofficial.patches : PoPOV - second build : Re: PoPOV - second build Server Time
18 Dec 2025 09:50:58 EST (-0500)
  Re: PoPOV - second build  
From: ABX
Date: 22 Oct 2002 10:07:07
Message: <s6marukag70bqj7aaagq6ttv9kq8cajsfc@4ax.com>
On Tue, 22 Oct 2002 15:50:34 +0200, Christoph Hormann <chr### [at] gmxde>
wrote:
> I'm quite confident there will be someone willing to make
> regular compiles with the intel compiler 

I hope too.

> > > You should really release
> > > the source code,
> > 
> > surprise at www.abx.art.pl/pov/popov :-)
>
> Thanks.  I had a first quick look:
>
> - renaming all file names to upper case is an *extremely* bad idea.

I not guilty. I did not changed it. It must be NT or Windows Commander.
I will automatize packing for future releases with some proces to control file
names

> - all changes seem well marked by #ifdef's but most of the modifications
> (counting number of blocks, not amount of code) are those preventing the
> warnings.  I don't want to warm up this discussion again, but for the sake
> of easy adaptation to new official releases (3.50c just came out) i think
> this should be dropped in a general patch collection.

Two solutions. First, I can remove my modifications and turn off warnings -
but then incorporating new patches can have some warnings I could not catch.
Second, I can remove old behaviours and stay with new syntax when it not
changes features. Personally I prefer second solution but temporary I stayed
with #ifdefs to highlight all places modified by me.

> - the 'patches.h' file seems a good idea, i just would wish a short
> description of the individual patches at each #define (i know it's in your
> repository but that's not the same as if it comes with the package).

I though about it and probably incorporate this

ABX


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.