On Thu, 9 Sep 1999, Jon Leech wrote:
> > How does libGL map a (number of) unknown (at libGL compile
> > time) extension function names to an equally unknown driver
> > DLL name, and load that - on query? On glGetProcAddress?
>
> Query GL_EXTENSIONS string to identify supported extensions, then
> query entry points corresponding to extensions used by the app.
Hmm - I guess we frown upon people ignoring GL_EXTENSIONS and
just checking for the NULL return from glGetFuncAddress to
indicate the absence of an extension?
If we do approve of that then we must say the glGetFuncAddress
is REQUIRED to return NULL for unsupported extensions - or
else I think there should be some words in the document to
SAY that you are still required to check GL_EXTENSIONS.
Painful though it is, I have to say that you should continue
to check GL_EXTENSIONS. The existance of a function in the
driver (which could be a function that exists but doesn't
work on your rev of board or something) - doesn't guarantee
it's a usable function.
> Once again: if they don't play by the rules of the ABI standard
> we're creating, they can't make use of it. Maybe everyone doesn't want
> to play and this whole effort is irrelevant, but I think it's pretty
> clear that there are plenty of companies and OSS projects who want to
> play.
YES!
"Just Say No" to kludges!
Steve Baker (817)619-2657 (Vox/Vox-Mail)
Raytheon Systems Inc. (817)619-2466 (Fax)
Work: [EMAIL PROTECTED] http://www.hti.com
Home: [EMAIL PROTECTED] http://web2.airmail.net/sjbaker1
