Many programmers think that the more error messages a static code analyzer produces, the better. It would be true if all the messages hit the bull's eye, as they say. But this is impossible: the same warnings may be considered both true and false by different programmers depending on the project type. There is also one more important and interesting thing. It may appear that a line between a false positive and a real error is very thin. Let's have a look at one of these cases.

Continue: http://www.viva64.com/en/b/0157/

Neo1

8/30/2012 2:11 AM EDT

Though I agree with the intention that getting bombarded by false positives is avoidable it's still better that the fear if uncertainty over unchecked code space.

Sign in to Reply