2 ms·
That's fine for an argument in a bar, and not so helpful for people who are doing software engineering with code that is developed under multiple compiler versi
by greglindahl 7y ago
That's fine for an argument in a bar, and not so helpful for people who are doing software engineering with code that is developed under multiple compiler versions. Or who build old code versions with a new compiler version.
- reitzensteinm 7y agoWhy are "people who are doing software engineering" expecting to build code in a new compiler without migration effort, and ignoring new warnings that have been added potentially pointing to existing undetected issues just so the code continues to compile? "People who want to get shit done", sure. Pragmatists, even.
- monadgonad 7y agoIt's only not so helpful because -Wall is badly named and now we're forced to deal with that legacy. Ideally, -Wall would be the same as clang's -Weverything, and there'd be a -Wstandard (or something) flag for what -Wall currently does.
- flukus 7y agoHow often do you get warnings that aren't either real bugs or trivial to fix anyway? The problem with ignoring warnings is that they tend to accumulate and before long you can't see the ones you really do need to pay attention to. And yes that means you have to take the time to cleanup on new compilers with more warnings.