Official feedback on OpenGL 4.1 thread

[randall]

Pointer _definitions_ in a header file...?

[ScottManDeath]

You could check for the GL_ARB_debug_output extension. On a non-WGL_CONTEXT_DEBUG_BIT_ARB context this extension is/should be not supported.

I am sorry, but i have to ask again: What about the headers?

-chris

I updated glew from the svn, put the ARB_cl_event extension on the black list and then ran the build script which fetches the extension.txt files and builds everything. I had to massage glew.h for the debug output callback typedef, but that was trivial. I could provide the generated files, if required.

[Chris Lux]

Thanks for the function pointer definitions.

I am not using GLEW or some other extension library anymore. I maintain a simple core-only lib for my projects, but parsing the spec files is still to much here .

[Alfonse Reinheart]

I was updating my spec files for 4.1, and figuring out which extensions were core extensions and which weren't. Then, I ran into, well, this in the vertex_attrib_64bit spec:

void VertexArrayVertexAttribLOffsetEXT(uint vaobj, uint buffer,
                                       uint index, int size,
                                       enum type, sizei stride,
                                       intptr offset);
 
(note:  VertexArrayVertexAttribLOffsetEXT is provided only if
EXT_direct_state_access_memory is supported.)

What is EXT_direct_state_access_memory?

[Groovounet]

I guess a subset of EXT_direct_state_access for buffer and texture DSA?

[elFarto]

I was updating my spec files for 4.1, and figuring out which extensions were core extensions and which weren't. Then, I ran into, well, this in the vertex_attrib_64bit spec:

void VertexArrayVertexAttribLOffsetEXT(uint vaobj, uint buffer,
                                       uint index, int size,
                                       enum type, sizei stride,
                                       intptr offset);
 
(note:  VertexArrayVertexAttribLOffsetEXT is provided only if
EXT_direct_state_access_memory is supported.)

What is EXT_direct_state_access_memory?

What's even more interesting is the wording in the NV_vertex_attrib_integer_64bit extension:

void VertexAttribLFormatNV(uint index, int size, enum type, sizei stride);
 
(note:  VertexAttribLFormatNV is provided only if
NV_vertex_buffer_unified_memory is supported.)

Which seems to imply that EXT_direct_state_access_memory is an analogue to NVIDIA's bindless extensions, although, I have to say there's something not quite right with that function if that is the case (why would you want a vaobj and buffer passed in?).

Regards
elFarto

[Alfonse Reinheart]

Which seems to imply that EXT_direct_state_access_memory is an analogue to NVIDIA's bindless extensions.

I thought that at first too. But if that were true, VertexArrayVertexAttribLOffsetEXT is not the right definition for it. It takes both a buffer object (by name, not by 64-bit pointer) and an offset, which VertexAttribLFormatNV (and the other FormatNV calls) do not. Indeed, not taking these parameters is half the point of bindless. This function is not structured like bindless calls are; it's a pure analog to DSA's VertexArrayVertexAttribOffsetEXT.

[Groovounet]

This function just look like the other DSA functions for VAOs.

[Don't Disturb]

Just came back from holiday and found out about ARB_get_program_binary. After asking for it for a long time this has made my month. THANKYOU!!!!!!!!!!

[tobindax]

The spec reads beautifully as an introductory text to the API for programming. However, it's pretty cryptic abruptly when it gets to 'projection'/transformation/viewports/"cameras". It could use an introductory paragraph or page about the way OpenGL sees things in that regard. I know it doesn't HAVE to, but it'd be nice.