Hi SunBlack (or whatever your real name might be), Static Code Analysis, such as CppCheck, PVS Studio, Lint etc, should not be considered 100% accurate. The many of the "errors" they report are often false positives, even if CppCheck is one of the more conservative static code analysis tools I have seen.
When I run static code analysis on my own code usually I consider the "errors & warnings" I get from the tools more as a suggestion to take a second look at my code to make sure that I haven't made any simple errors. So often what the static code analysis tools actually is saying is more like: "This piece of code looks odd. Are you sure this is correct?" Since OpenSceneGraph is open source there is nothing stopping you from fixing any legitimate problems yourself and send in your contribution to the submission mailing list together with an explanation of what you have done. But I think you will have a hard time to convince Robert Osfield (who is the project lead for OSG) to make any broad changes to the code solely based on warnings from CppCheck (or any other static code analysis tools). Regards, Björn ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=60616#60616 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
