You are right, ifdefs are a bad thing and I think that everyone is aware of that. Luckily C++ offers more elegant ways around this .. the problem in general I think is time.
There is the problem of getting all these new features in as fast as possible (using ifdefs) or to keep the code clean.
Maybe there should be a feature freeze and cleanup phase, (oh well, how boring ..)
Guenter
On Mon, 2 Jun 2003, chris clepper wrote:
Hi
The code in pix_texture has become appalling - the ifdefs have made it completely unreadable. Whoever has been doing #if 1 and #if 0 please remove this and decide what code you want to commit before committing it. There seems to be some sort of bracketing problem that causes crashes but it's really nearly impossible to trace it due to the ridiculous number of #ifdefs. If you have added #ifdefs to the code please go back and comment them for the other devs.
I'm about to write OSX only texturing objects because it's pretty obvious to me that texturing is OS dependent at this point. Maybe in the future this will change but this current ifdef hell is doing no one any favors at this point.
cgc
GEM-dev mailing list GEM-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/gem-dev