| The cleanest way to resolve this so it never comes back is to include
| glext.h in gl.h, bite the bullet and port whatever code breaks. (ducks for
| cover)
|
| If we want glext.h to become a cross-platform thing, then we need a
| cross-platform symbol. On this much we agree.
Mark & Michael can you comment on what nvidia's plan is wrt
extension definitions on Windows? I'm guessing that the
plan was to include a glext.h on windows too, but not
modify the system version of gl.h It would seem that
GL_HAS_GLEXT or some other symbol wouldn't be in the
Windows gl.h nor would an include of GL/glext.h and
application writers would still need other mumbojumbo
to achieve portability. True or False?
Note, my preference is to include glext.h in gl.h on linux and
fix the broken programs too with the assumption that linux
provides the preferred model for how things should work. I have
100 odd programs that may or may not need fixing -- they already
needed a whole bunch of fixing to appease gcc on linux, and then
more to make them work with cygwin so i'm used to the idea that
they need continuing maintenance.
david
