For the record, I was quoting the latest GLSL 1.50 spec, so "gl_" is
reserved, even for current OpenGL 3.2.
If OSG provides a mechanism that allows the user to specify the names
that matrices are associated with, then OSG could go ahead and violate
the spec and use "gl_" names by default, but apps would still have the
flexibility to be spec compliant and change the names if they desired
to do so.
Jason Daly wrote:
Robert
Osfield wrote:
If GL3 isn't providing any gl_ uniforms
surely they can't be reserved,
you can only reserve something if it might exists. I can see why gl_
will be reserved for GL2, but I can't see the issue for non backwards
compatible GL3.
It doesn't provide uniforms, but there are gl_* identifiers still in
use (gl_Position, for example).
Besides, it doesn't really matter whether we think it's an issue or
not. If the spec says they're illegal, then the GLSL compiler will
likely throw an error any time a shader tries to use one that's not
declared by GL itself (I haven't tried this personally, but that's what
I would expect)
--"J"
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
|
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
