| Weekly edition | Kernel | Security | Distributions | Search |
| Archives | Calendar | Subscribe | Write for LWN | LWN.net FAQ |
Quote of the week
Quote of the week
Posted Feb 28, 2008 13:22 UTC (Thu) by davecb (subscriber, #1574)Parent article: Quote of the week
This is one of the reasons that I and my colleagues like semi-automated error/portability analyses with a human in the loop to provide judgement. The process and the tool are described, in the context of porting, at <self-aggrandizing plug> http://datacenterworks.com/stories/port.html </self-aggrandizing plug> --dave
(Log in to post comments)
Quote of the week
Posted Feb 29, 2008 14:19 UTC (Fri) by vonbrand (subscriber, #4458) [Link]
Very nice tools! I'll dig into them later.
Quote of the week
Posted Feb 29, 2008 14:58 UTC (Fri) by davecb (subscriber, #1574) [Link]
I'm also reachable as davecb@spamcop.net or @datacenterworks.com
Quote of the week
Posted Mar 2, 2008 11:00 UTC (Sun) by joern (subscriber, #22392) [Link]
What caught my eye in the first couple of lines was this: "fixing compiler error messages". Which is an excellent description of the actively harmful behaviour my quote was about. "Fixing" compiler warnings gives your brain the same quick high that a heroin fix will - and is just as useful. There simply is no fix for a compiler warning. _Code_ may be buggy or have poor style. Code can be fixed. Compiler warnings are just that: warnings. They may be valid, they may be invalid and they may point to something much more interesting in near vicinity. But the strange idea that warnings can be fixed in any shape or form is plain wrong. And mechanically going through the compiler output, randomly changing code until miraculously all warnings disappear is far too common a mispractice to treat it with lenience. DO NOT FIX WARNINGS! Fix code.