| > I say we require a NON-null return (that is in fact the only truely context
| > independent possibility) which will either noop or error (to address your
| > concern).
| 
|     The noop *is* my concern.
| 
| > This removes the requirement for NULL test AND the temptation to
| > incorrectly associate getProc with getString as the appropriate means to
| > determine exsistance of an extension.

I think it may be difficult to return all a noop for all implementations.
if the API implementation used the equivalent of WINAPI (stdcall) calling
conventions (callee pops parameters), a generic noop routine doesn't leave
the stack in the correct state.  On the other hand maybe only Windows has
this problem and all other implementations use caller pops parameters
instead?
        -db

Reply via email to