[osg-users] OpenGL ES-2.0, OpenGL ES-1.1 and OpenGL 3.x support now ready for testing :-)

E. Wing ewmailing at gmail.com
Fri Nov 20 13:49:18 PST 2009

> I understand. I just thought calls named "_NSGetEnviron" and
> "exc_server" (those are the calls they refer to in the article) sounded
> like "get some environment variable" and some threading functions, so I
> thought it might be possible that the low-level implementations of some
> functions might use them without us being aware of it...
> But if the likeliness of that happening is close to null, that's great.

It will be very explicit whether you are using a "private" API or not.
There won't be a header definition and you will get a compile error.
If a public API calls a private API behind the scenes, that is
perfectly okay.

I expect the only areas OSG will have trouble is with the module
loading systems (osgDB), but we already expect that.


More information about the osg-users mailing list