On Tuesday 05 April 2005 19:03, Ian Romanick wrote:
Adam Jackson wrote:
I have another one: Hide all the functions that start with XF86DRI*, and expose them to the driver through a function table or glXGetProcAddress rather than by allowing the driver to call them directly. This will simplify the case where the X server is itself linked against libGL.
Kevin tells me these functions were never intended to be public API anyway.
The only functions that are still used by DRI_NEW_INTERFACE_ONLY drivers are XF86DRICreateDrawable, XF86DRIDestroyDrawable, and XF86DRIDestroyContext. It should be easy enough to eliminate those, but something other than gLXGetProcAddress might be preferable.
Yeah, I just threw out glXGetProcAddress as a suggestion. It's probably better to pass this table into the driver through the create context method.
We can't eliminate the functionality of these calls (I don't think), but they should not be visible API from the perspective of the GL client.
Right. glXGetProcAddress() should not be used by libGL or the drivers to get internal function pointers. There should be a new function for that, if we're breaking the ABI.
-Brian
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
