On Fri, 17 Mar 2000, Jon Leech wrote:
> On Fri, Mar 17, 2000 at 09:51:13PM -0800, Mark Kilgard wrote:
> > Without GL_HAS_GLEXT, it is impossible to portably know if <GL/glext.h>
> > can be included without a compile-time error.
>
> Au contraire; the symbol has no utility for portable source code.
> For an oglbase environment, it is not needed. For any other environment
> (read: Windows, MacOS, vendor UNIX), it is highly likely that the symbol
> will not ever be put in gl.h, *just as no other guarantees of oglbase
> are meaningful for such an environment*.
...and on a Linux/UNIX box, you can always use an external configuration tool
like autoconf/automake to decide whether the glext.h file *actually* exists and
provide a '-D' directive where needed. That's far better than defining a symbol
in gl.h that could be lying to you if some dumb user either copied gl.h from
another machine/directory or something.
Steve Baker (817)619-2657 (Vox/Vox-Mail)
L3Com/Link Simulation & Training (817)619-2466 (Fax)
Work: [EMAIL PROTECTED] http://www.hti.com
Home: [EMAIL PROTECTED] http://web2.airmail.net/sjbaker1
