Without Warning: Keeping the Noise Down in Legacy Code Builds

By Guy Bolton King

As part of the process of taking the legacy out of a legacy code base, we want to remove all compiler warnings. However: a crude approach of merely switching them off helps no-one; we don’t necessarily have the time to actually fix the warnings (because to do that may break "working" code, and would thus require writing tests); and we want those warnings on and actionable for new code that we write. This short session will present a handful of tools and techniques for getting a quiet compile without losing the warnings we want or introducing changes in code behaviour.