| I am not aware of a precedent for any piece of state returned by a context
| being applicable to any other context, with the noteable exception of
| shared display lists and texture objects.  In these exceptional cases,
| there are well defined criteria for sharing, and coincidently, these shared
| contexts can also share ext function ptrs.

I have a different perspective which I did try to state before.  The returned
function pointer is part of the client-side library binding, not unlike
the defined API entry point symbols.  If you believe they are similar
then you can argue for similar behavior.  I believe it is completely
appropriate to separate them from the notion of extension presence
in the same way that the regular client side bindings are independent
of whether the context supports the extension ...
        david

Reply via email to