In Visual Studio 2008 Team System, I just ran Code Analysis (from the Analyze menu) on one of my C# projects.One of the warnings produced was the following:
I have an abstract class that implements IDisposable, like so: publ开发者_开发知识库ic abstract class ConnectionAccessor : IDisposable
I want to write a semantic patch for coccinelle, so that it will add if (ptr == NULL) ... checks after calls to malloc where they are missing.
I am looking to write a static analyser for a university class. To provide more power for the tool I would like to be able to look up the call hierarchy (as Ctrl+Alt+H does in Eclipse).开发者_运维百科
I\'m in a situation where I\'m required to make at least s开发者_开发技巧ome effort to remove never-used code from my source code.The general preference is to use a static code analysis tool.We\'ve ha
my project includes a simple C file with a header. Like this: #ifndef __IMAGE_ARRAY_3D #define __IMAGE_ARRAY_3D
We\'re using VS2008 with the built in static code analysis rule set. We\'ve got a relatively large C# solution (150+ projects) and while some of the projects (< 20) are using static code analysis r
I wish to add a PMD check to ensure that a class does not have too many public methods, but I do not want constructors and getters/setters to be included in the check.
A lot of what I have learned about VB I learned from using Static Code Analysis (Particularly Aivosto\'s Project Analyzer). And one one of things it checks for is whether or not you cleared all object