Follow-up Comment #3, patch #3468 (project freeciv):
Looking at the clang warnings lists I'm inclined to say that clang clean build
should not be goal for us, or at least many warning types should be silenced
with -Wno- -options instead of reworking the code to avoid the warning. For
instance the "tautological compare" warnings because macro expansion often
leads to value being compared to itself seem more like something that compiler
should use for optimization, not to nag developers about. To work around them
would make code much more complicated and likely introduce a lot of real bugs
while fixing none.
Reply to this item at:
Message sent via/by Gna!
Freeciv-dev mailing list