>Since the return value of GetProcAddress is context-independent, there
>is no reason to require a currently bound context to call it.

Although a supporter of context-independent pointers I disagree with this. I
believe all the rules for having a bound context remain in force. Why? Because
the context may have to register its extensions with the "API". Until the first
context that exports the entry point in question has been bound it won't be
known to the API. So a NULL or non-NULL pointer could be returned depending on
what occured previously, if you don't bind YOUR context first.

> I have to stand up and count
> myself among the supporters of context-independent function pointers.
> For me, the compelling argument is that without context-independent
> pointers it's very difficult to design libraries that are capable of
> handling multiple contexts efficiently.

I agree with Allen.

John

Reply via email to