Bryan Turley

I have thought about doing that myself, I don't think it would be very hard for Glow to output that. The reason I am not is https://www.opengl.org/registry/specs/ARB/direct_state_access.txt Nearly all of...

Anything that supports GL4.1 is API compatible with GLES2.0. GLES3.0 -> GL4.3 GLES3.1 -> GL4.5 When they made gles2.0 they started around gl3.2 core and stripped out features. The only...

Oh wait... that is a precursor for the patch I would submit when it gets resolved nevermind on that. Think people are shut down for xmas.

I should note the strongest reason for doing this would be windows. If you have mutliple gpus of different families/vendors the pointers you get from wglGetProcAddress() may be different per...

Beyond that in my newest binding generator I dropped the entire idea of having individual pointers. Going from individually named function pointers to a sized array (not slice) of functions...

This code is dead don't use it for anything but an example on how I solved this problem. https://github.com/bryanturley/old_gl/tree/master/glx14 (all cgo based, no asm) funcs.go and enums.go are generated from...

I think you should end them in Go like I do. I was treating them as an automatically generated extension. EXT_automagic_go ;) It would be nice if current and future...

@capnm: Since glow is part of go-gl now, it would probably be best to post this kind of message on the go-gl mailing list instead of in an issue tracker....

Nevermind about holding off seems a copying/moving GC won't happen till go 1.6 a full year away.

I was going to make a global io.Writer and change all the Printf to Fprintfs as well.