I’ve tried the suggestion to treat warnings as errors, but I’ve never liked it. I have two reasons:
I like to use the
#warning do something important herepragma when I’m doing the initial scaffolding for a bunch of new classes. It’s my in-code to do list, better than the old-and-busted
FIXMEcomment because it shows up in every build.
If you can check-in code with warnings and still sleep at night, you might want to think about a new profession. And if you can ship code with warnings in it, then you seriously need to get your head checked.
In other words, it’s overly pedantic during the early stages of development, and completely superfluous during the final stages. Warnings are warnings, errors are errors, they’re different, and I’m OK with that.