I am really astonished by the capabilities of static code analysis. The tool surprised me the other day as it turned out to be smarter and more attentive than I am. I found I must be careful when working with static analysis tools. Code reported by the analyzer often looks fine and I'm tempted to discard the warning as a false positive and move on. I fell into this trap and failed to spot bugs...Even I, one of the PVS-Studio developers.
So, appreciate and use static code analyzers! They will help save your time and nerve cells.
[Ed note: I debated running this story as there was an element of self-promotion (aka Bin Spam), but the submitter has been with the site for a while and has posted informative comments. Besides, I know there have been far too many times when I've seen a compiler complain about some section of my code and I'm thinking there is nothing wrong with it — and then I, finally, see my mistake. Anyone have samples of code where you just knew the compiler or static analyzer was wrong, only to find out otherwise? --martyb]
(Score: 3, Informative) by The Mighty Buzzard on Monday October 23 2017, @10:47AM (1 child)
This almost got chucked as spam but martyb thought we could make a decent discussion out of it. Don't look for him to go pushing out anything they submit though.
My rights don't end where your fear begins.
(Score: 0) by Anonymous Coward on Tuesday October 24 2017, @12:05AM
Yeah. When I saw it in the queue, I wondered if it would make the cut.
It has stirred some interesting discussion, so it appears that the proper choice was made.
What I was hoping to see was the names of some tools in use.
Comparisons by folks who had tried multiple apps would be especially interesting.
Licenses (FOSS|proprietary) and license costs would add a dimension as well.
(Envying the larger userbase of the other site here.)
The Wikipedia page linked in TFS has an External links section, but I was hoping to see a link to a "Comparison of..." Wikipedia page there.
-- OriginalOwner_ [soylentnews.org]