At 08:38 AM 10/15/99 -0500, Stephen J Baker wrote:
>
>With this mechanism, it's probably no biggie whether the pointers are
>context-dependent or context-independent.  The library needs to be
>told which context it is bound to in order that it can use the
>right set of extensions for the current context - that's a pain
>but it's inevitable if you allow heterogeneous renderers.

I have nothing to add to this paragraph, but thought it was worth reading
twice.  =)

I would be content with context-dependent glGetProcAddress, as originally
spec'ed.  Portability issues are addressed (i.e. no glX vs wgl vs agl) but
the app needs to manage per-context pointers along with the rest of
per-context state it must already manage.

Reply via email to