I work on a C++ project that generates bajillions of warnings. Most of the warnings appeared after the code was written:
- Initially the project used Visual C++ 8, soon switching to 9, but there is little difference in the generated warnings. Warnings were either fixed or silenced, so there were no warnings then.
- Then a 64-bit target was added. It generated a huge amount of warnings, mainly because of sloppy use of types (e.g.
size_t). No one bothered, or had time, to fix them once the code worked for the purpose.
- Then support for other platforms using GCC (4.5 and 4.6, some 4.4 initially) was added. GCC is much more picky, so it generated many more warnings. Again nobody bothered, or had time, to fix them. This was complicated by the fact that GCC didn't have a pragma to silence a warning in particular bit of code until 4.5, and according to the documentation it is still not what one would need.
- In the mean time some deprecated warnings popped up.
So now we have a project generating thousands of warnings. And I can't even say from how many places, since even
.cpp files are compiled several times by different compilers and warnings in headers get printed over and over.
Is there a best practice for cleaning up something like that? Or at least some positive experience dealing with it?