Hello, On Mon, Jul 1, 2013 at 11:43 AM, Robert Osfield <[email protected]> wrote: > Which warnings cause more problems than they worth is very much a case > by case issue, blanket warning suppression is bad, local warning > supression is better. For instance not having users suppress warnings > when compiling against the OSG is ideal, so the are headers need to be > pretty clean, but warnings in our .cpp's that we know are unhelpful > would be more appropriate for suppression.
Yes, agreed. What I had in mind was to use the compiler switches locally within the offending modules, not globally on the entire codebase. Sometimes one gets warnings from external libs (like Collada, OpenVRML or FBX) while compiling OSG, so it helps to be able to selectively disable them. Regards, Jan _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
