On Fri, 10 Sep 1999, Thomas Roell wrote:
> > OK - but you still have to call the gl version from the context in
> > which you'll call the function that it returns. (That would certainly
> > HAVE to be the case for EXT functions - so we might as well make
> > it the rule for all functions - if only to simplify the manual!)
>
> It's still an ugly problem. For an application programmers point of
> view, I really don't like the idea of GetProcAddress() be dependant
> upon the context it's called under. It's just a nightmare and a
> predictable recipe for disaster. On the other hand, letting libGL do
> the indirection for unknown extensions is very tricky.
On the other hand, MANY programmers only ever work in one context,
and if they use GLUT, they aren't even aware of the existance of
contexts and such.
Relatively few programmers (I suspect) are into multiple contexts,
and if they are, will be painfully aware of the consequences of
getting things like this wrong.
Look at it this way: All of the other gl* functions are assumed to
be "in the present context" - why should glGetFuncAddress be any
different?
We are not demanding to have:
glGetError ( context, ... ) ;
glAreTexturesResident ( context, ... ) ;
...etc?
Is this really all that different?
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
