In your message of 17 September 1999 you write:

> Hi All,
> 
> Let's rein this back a little.  It has been adequately proven (to me) that both
> context-specific and context-independent specs *can* be implemented
> successfully and with equivalent run-time efficiency.  If we can agree on
> that, we can drop the implementation discussion and concentrate on what
> is the right thing to do in terms of the OpenGL API.
> 
> Shall we try to have a more concise discussion addressing just the API
> considerations?
> 
> 
> ########
> 
> 
> For the record, here's my super condensed opinion:
> 
> In a single screen, homogeneous driver environment, it makes no difference.
> 
> In a multi screen, heterogeneous environment, glGetString may return different
> extension strings for different contexts, therefore glGetAnythingEXT
> must return context-specific information.  An app must check the extensions
> per-context, so it must do *all* its extension specific setup per-context, including
> obtaining function pointers.

I fully agree here with you. The only thing where I'm a little bit
hung up is whether core API functions retrieved via
glXGetProcAddressEXT() are also context dependant.

- Thomas
-- 
             Thomas Roell   /\         An imperfect plan executed violently
             Xi Graphics   /  \/\ _     is far superior to a perfect plan. 
         [EMAIL PROTECTED]   /   /  \ \     
                         / Oelch! \ \             George Patton

Reply via email to