[GEM-dev] pix_texture

[Daniel Heckenberg]

Hi All,

I would certainly hope that we can avoid both #ifdef NIGHTMARES and
splitting the code object by object on platform lines.  Both of these
approaches are hard to manage in the long run.

If we can characterise the different behaviours of each platform and make
the code behave accordingly at run-time that would be great.  One example
that comes to mind at the moment is the vertical flip required for quicktime
images.  That's not so much a platform issue as a behaviour (QT for Windows
and DirectShow (sometimes) return "upside down" images).  Writing completely
separate OS-dependent classes won't help in that situation.

It's a similar situation with extension support I guess...

Daniel

On 2/6/03 7:45 PM, "guenter geiger" <geiger at xdv.org> wrote:
> 
> 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
>