Brian Paul writes:
> > > #ifdef linux
> > > #define wglGetProcAddress glXGetProcAddress
> > > #endif
> I'm against this sort of #ifdef'ing.
So am I. It's reality, though. As is maintaining function pointers.
> Also, any reference to glXGetProcAddress or
> wglGetProcAddress in a GLUT-based program sticks out like a sore
> thumb.
glutGetProcAddress() wraps it and hides it easily.
This is no good reason in my book.
> Unfortunately, use of wglGetProcAddress may be unavoidable
> for some time to come.
Exactly. So intead of one entry point, we have several.
> I'm in favor of separate glGetProcAddressEXT, gluGetProcAddressEXT,
> glxGetProcAddress, etc functions.
There has to be a good technical reason then why
glxGetProcAddress isn't sufficient? If there is
overlap, or if wglGetProcAddress implements the
combination of glxGetProcAddress or glGetProcAddress,
any GLUT wrapper or in-app abstraction will be an even
bigger pain. How soon will be see this adopted on
"other UNIX and Windows"?
b.
