David Brown wrote:
On Mon, Mar 31, 2008 at 04:48:22PM -0500, Gabriel Sechan wrote:
Rephrasing: 99% of the time, the code in that situation *is* correct.
It's only rarely an error. The correct answer is to flag it for human
checking, but to allow it, which is what a warning does.
My general experience is that warnings are either ignored, or the comiler
is configured to treat them as errors and they get fixed.
Alternatively you can reconfigure the programmers. :-)
Good programmers learn to look at warnings, verify if they are actually
pointing to a problem or not, and then turn off the warning with the
appropriate pragma/directive (along with a comment explaining why what
they are doing is okay).
Bad programmers can find ways to screw things up even when the compiler
gives them errors. ;-)
--Chris
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
