Stuart Anderson writes:
 > I agree. The existing API will have to handle multiple context/multiple screen
 > without adding a context parameter, so the pointer returned by GetProcAddress()
 > should be no different.

The overhead of per-context pointer switching will be there. The
question is, make it inherent to the API, or is it something the
application has to add when needed. This is a call-intensive
API, if another indirection becomes mandatory even for a
single-context application, it might hurt? I can understand
that people maintaining a dozen contexts would rather have
this convenience, but there are also games, and the ones I
have dealt with already have a lay that could easily handle 
this case for multiple contexts (w/o another indirection even).

 
                                          b.

Reply via email to