[osg-users] ShaderComposer::releaseGLObjects warning

Robert Osfield robert.osfield at gmail.com
Wed Apr 27 11:29:17 PDT 2016


Hi Andy,

On 27 April 2016 at 19:09, Andy Skinner <Andy.Skinner at mathworks.com> wrote:

> Yes, the "using" statement does quiet the warning.
>

Good to hear.


>
>
> Does that mean this is the solution, or that this just shows that there
> isn't a problem?  The reason I ask is that we've discussed the "using"
> statement for things like this before, and I don't believe you were in
> favor of it.  But using it would let us remove a bunch of warning handling
> in our use of OSG.
>
>
Needing to put a using in lots of places across the OSG to just quieten
inappropriate warnings is pretty crappy.  The more superfluous code you
have in your code base the less easy it is to read, the easier it to
break.  This makes me very wary of jumping through hoops to quieten dodgy
warnings from the compilers.

Robert.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20160427/a2154f67/attachment-0003.htm>


More information about the osg-users mailing list