On Oct 13, 2009, at 10:52 AM, John McCall wrote: >>> >>> Hmm, probably. I'll do that. >> >> Thanks, if there is too much screaming, we can always turn it back >> off by default :) > > That's not a bad general policy for warnings — if it's likely to > catch real bugs (i.e. is not just a suggestion), and it doesn't have > significant false positive problems (as measured by developer > screaming), turn it on by default. Maybe with an exception for low- > benefit high-cost warnings.
Exactly. Clang defaults a lot more warnings to on than GCC does for precisely that reason :). Particularly with good -W options, people should know how to shut them up if they really don't care. -Chris _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
