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: 0) by Anonymous Coward on Tuesday October 24 2017, @02:32AM (1 child)
My god! Was radio that long ago?
But I was mistaken. The discriminator (demodulator) is after the tuner.
(Score: 0) by Anonymous Coward on Tuesday October 24 2017, @04:34AM
And you blame Millennials, when truly, Grandpa, it is your own memory that fails you! Do you remember when blacks knew their place? Do you remember when America was a White nation, with a White President, and a White House with a White Dog? And now all we have is an Orange President, with some ex-Commie Bimbo first Lady, and no dog! Why does the president not have a dog? So, yeah, Nazis are totally cool now, until someone threatens to "punch them in the face!" [youtu.be]
Take it off, white boy, take it off!