4 ms·
Absolutely. One strategy I employed with a very old code base with a gajillion warnings was to output them to a file and compare against a reference file at th
by jahnu 5y ago
Absolutely.
One strategy I employed with a very old code base with a gajillion warnings was to output them to a file and compare against a reference file at the end of the build. If the output changed we would fix those and maybe any that kept happening if you added new compilation units etc. It at least helped us slowly reverse the trend of accumulating warnings.
- lelanthran 5y agoI did the same, but it meant that the build could not go in parallel. I also stored the warnings.txt in git so that before any commit I could simply do a git diff to see what warnings were changed by my additions.