| > 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
- Re: [oglbase-discuss] New GLX_AR... Brett Johnson
- Re: [oglbase-discuss] New GLX_AR... Jon Leech
- Re: [oglbase-discuss] New GLX_AR... Brett Johnson
- Re: [oglbase-discuss] New GLX_AR... Michael I. Gold
- Re: [oglbase-discuss] New GLX_AR... Brett Johnson
- Re: [oglbase-discuss] New GLX_AR... Michael I Gold
- Re: [oglbase-discuss] New GLX_AR... Brett Johnson
- Re: [oglbase-discuss] New GLX_AR... akin
- Re: [oglbase-discuss] New GLX_AR... Brett Johnson
- Re: [oglbase-discuss] New GLX_AR... David Blythe
- Re: [oglbase-discuss] New GLX_ARB_get_proc_addres... David Blythe
- Re: [oglbase-discuss] New GLX_ARB_get_proc_addres... Stephen J Baker
- Re: [oglbase-discuss] New GLX_ARB_get_proc_address specifi... Ron Bielaski
- Re: [oglbase-discuss] New GLX_ARB_get_proc_address sp... Stephen J Baker
