While digging around for information on extension loaders, I eventually found a reference to the following from the wglGetProcAddress() documentation:
Remarks
The OpenGL library supports multiple implementations of its functions. Extension functions supported in one rendering context are not necessarily available in a separate rendering context. Thus, for a given rendering context in an application, use the function addresses returned by the wglGetProcAddress function only.
The spelling and the case of the extension function pointed to by lpszProc must be identical to that of a function supported and implemented by OpenGL. Because extension functions are not exported by OpenGL, you must use wglGetProcAddress to get the addresses of vendor-specific extension functions.
The extension function addresses are unique for each pixel format. All rendering contexts of a given pixel format share the same extension function addresses.
Is this really a concern, or is it pretty much safe to build a set of function pointers once and just keep using them.
It looks to me from the above that there is no truly kosher way of using the WGL_ARB_pixel_format functions.
Originally posted by gdewan: It looks to me from the above that there is no truly kosher way of using the WGL_ARB_pixel_format functions.
I also noticed that some time ago and went to my teammates asking them if I could end up with useless pointers. After some days spent on researching the subject, the conclusions were that:
1- Officially, sharing pointers between different contextes is a call for trouble.
2- De facto, vendors are making our life easier by not changing their function pointers so, just select the pixel format with some care and everything should work fine.
3- Everyone is doing it possibly without realizing what’s going on and still works. So, why should I really care? If it crashes, I’ll fix but until then I’ll live with this.