Hi Pjotr, On 31 May 2013 08:09, Pjotr Svetachov <pjotrsvetac...@gmail.com> wrote: > This is actually an issue with the visual studio 2012 library, see here for > an explanation: > http://connect.microsoft.com/VisualStudio/feedback/details/733720/
Thanks for the link, explains the tangled mess of hacks that got MS into a situation where valid code produces irrelevant warnings... umm.... sounds like they've been making some great engineering decisions! So.. for us we either stop inheriting from fstream etc. or we disable the warning locally using a #pragma. We already have a series of #pragma for windows in include/osg/Export. We could easily add 4250 to the list of disabled warnings. I'd rather keep disabling warnings to the minimum, perhaps a local #pragma that is just set for the include/osgDB/fstream header. Can we push/pop #pragma's under Windows? Robert. _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
