Re:GCC 6 Will Warn You About Misleading Code Indentations
by tomjakubowski on Sunday January 10, 2016 @04:44PM
(#10877347)
From the article:
> This new warning isn't enabled by default.
And even if it were, it's a matter of adding -Wno-misleading-indentation to make builds green again. Not a big deal. And besides, it's likely that fixing those warnings could be done mechanically. (and it's hardly true that every project that ships with -Werror has such misleading indentation somewhere in its code)
Re:GCC 6 Will Warn You About Misleading Code Indentations
by cperciva on Monday January 11, 2016 @01:04AM
(#10879117)
And even if it were, it's a matter of adding -Wno-misleading-indentation to make builds green again
How does that help the person who is building the release you shipped six months ago with a new compiler?
Re:GCC 6 Will Warn You About Misleading Code Indentations
by legulere on Sunday January 10, 2016 @05:08PM
(#10877456)
You should have -Werror enabled on debug builds when developing and disabled on release builds.
Re:GCC 6 Will Warn You About Misleading Code Indentations
by MereInterest on Sunday January 10, 2016 @06:26PM
(#10877742)
Huh. I would think it to be the other way around. When debugging, let me comment stuff out without erroring due to an unused variable or an unused parameter. Let me use a C-style cast to check the bit representation of an object. Then when building the release build, enable -Werror to make sure that I'm not sweeping anything under the rug.
THIS IS WHY YOU SHOULD NOT USE -Werror. NOT EVER. (And if you can't bring yourself to do anything about mere warnings, you shouldn't be in software engineering.)