Re: [AD] What to do about gl_ext.h

2016-10-17 Thread SiegeLord
There are two issues. First, as it stands now, if you add a new extension/api, it inserts a field in the middle of types like ALLEGRO_OGL_EXT_LIST, which breaks the al_get_opengl_extension_list ABI. This is fixable through the use of a python generator of some sort which would always add new t

Re: [AD] What to do about gl_ext.h

2016-10-16 Thread Elias Pschernig
What exactly is the problem with the ABI there again? Each OpenGL extension is basically a set of GL_* constants and a set of gl_* API entries. Since those API entries are loaded at runtime, Allegro provides a function pointer for each which is filled in when it loads them. Every time a new extensi

[AD] What to do about gl_ext.h

2016-10-16 Thread SiegeLord
A little while ago I sent out a patch to revert Elias's addition of the various multisampling/depth buffer additions to gl_ext.h (and the associated headers) as it broke ABI compatibility. Those additions were obviously useful, and it'd be a terrible state of affairs if we couldn't ever add any