Hi Jean-Sébastien, Just to let you know that you're not alone to see those Warning, I'm seeing them too under VS 2008 with 32bits build...
You can hide them using option : /wd 4312 Kind regards, * * 2010/1/11 Robert Osfield <[email protected]> > Hi JS, > > On Mon, Jan 11, 2010 at 2:41 PM, Jean-Sébastien Guay > <[email protected]> wrote: > > So would you accept a change that pushes the warning disable state at the > > start of include/osg/State, disables that warning for the file, and pops > the > > warning disable state at the end of the file? (or perhaps only in those > > functions would be less prone to hiding other problems) > > Jikes, no way. Hacks like that stays well out of general OSG headers. > > Disabling warnings in specific .cpp's where there are problems is > acceptable. If that's not possible then placing a global disable in > the CMake build or the include/osg/Export. > > > You've refused such changes in the past, but perhaps for this case it's > the > > only way to go... > > Having yet another example of how crappy compilers can be doesn't > change my opinion on putting hacks into the OSG headers. > > Robert. > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > -- Alexandre AMALRIC Ingénieur R&D =================================== PIXXIM S.A. 73E, rue Perrin-Solliers 13006 Marseille http://www.pixxim.fr
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
