Re:Apple's SSL/TLS bug
by erichurkman on Saturday February 22, 2014 @12:01PM
(#7282638)
And if you are going to disable a specific warning, it should only be for a limited section of code and include a detailed comment about why the warning is superfluous and why the code is safe.
> That's a rare problem among developers.
Many of the C guys I met along my career thought otherwise.
> Static analysis, regression tests and turning on all the warnings you possibly can should be mandatory, especially for such critical pieces of code.
+1
Static analysis, regression tests and turning on all the warnings you possibly can should be mandatory, especially for such critical pieces of code.