> I could kinda see a case to #include glext.h in gl.h in
> the oglbase
> environment only, but it raises problems for whomever is
> providing gl.h
> since glext.h is expected to be replaced over time - replacing system
> components is a nightmare for support people.
Is glext.h a system component or not? If yes, we should include it from
gl.h. If not, we shouldn't define a token which guarantees its existance.
We can't really have it both ways.
What's the difference between replacing gl.h and replacing glext.h, if both
are system components?
(I'm okay with calling glext.h a replaceable system component and including
it from gl.h)
