In your message of 21 March 2000 you write:
> I can think of one reason why you must NOT #include glext.h from
> within gl.h and that is that it could wreck existing programs
> that conditionally compile extension code on the assumption
> that they will be compiled and run on the same machine.
>
> #ifdef GL_EXT_something_or_other
> glSomethingOrOtherEXT () ;
> #endif
>
> Since glext.h defines ALL extensions for all machines, an
> existing program that was only intended to run on the machine
> it was compiled on would certainly break if glext.h were
> rammed down it's throat by virtue of forced inclusion within
> gl.h.
Correct. As far as we discussed before, glext.h MUST include gl.h.
Also remember that glext.h should not declare extenion functions, but
only define the pointers to a specific function as they are queried by
glXGetProcAddressARB(). So normally there wouldn't be any declarations
for those extension functions.
So I guess we are back to Jon's original point that a compliant
implementation always ships a glext.h by default.
- Thomas
--
Thomas Roell /\ An imperfect plan executed violently
Xi Graphics / \/\ _ is far superior to a perfect plan.
[EMAIL PROTECTED] / / \ \
/ Oelch! \ \ George Patton
