pstolarc at theperlguru.com wrote: > On Sat, 31 Aug 2002, Mark Wedel wrote: > Yes. Windows has it's own DATADIR defined somewhere that does something > else. I don't know what it does. It's in some standard library. It > didn't appear to be worth the time it would take to work around. Fair enough. >> ifdef <few lines> else <few lines> endif >> <few more lines of code that are common >> ifdef <few lines> else <few lines> endif >> >> etc, such that it became really hard to read through the function to see what >> it was doing, because not only did you have to try to parse the code, but you >> also had to parse the ifdefs. So I tended to prefer longer ifdef/else/endif, >> even if they included some common code. > > > I don't think I did that to the server source. It's probably some other > Win32 guy. We all look alike. Actually, I was thinking that this predated the win32 changes - there was code like that in for some of the different config options. It doesn't really make too much difference what the code is ifdeffing - it was mostly just a readability issue. > I would guess MacOS would build from the Unix source, as there is no GUI > code in the common files, but that's just a guess. Yeah - I notice there are a few 'getenv()' calls in the common/init.c and image.c files. I'm not sure how they would get handled on macos.