Without Warning: Keeping the Noise Down in Legacy Code Builds

on YouTube ↗16m

" summary

Legacy build starts with a nightly non‑incremental full build that pipes compiler output into a script summarize_warnings to baseline 6,000+ warnings and find hotspots (one file had a 4,000‑line function producing thousands). Teams choose which warnings to fix and which to quiet; a second script suppress_warnings inserts localized suppressions (MSVC pragma warning / clang push/pop) rather than global compiler flags. New builds treat warnings as errors per project/file so new code cannot introduce warnings. Scripts (PowerShell) and examples live on GitHub.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 0:23What Do We Mean by Legacy Code
3. 0:54Static Analysis
4. 12:52Summary

" related talks

• 01h 31mClean(er) Code for Large Scale Legacy ApplicationsArne Mertz · ACCU 2019
• 27mMobiconf 2018: Carola Nitz, VideoLabsCarola Nitz · Mobiconf 2018
• 55mSo, you inherited a large code base...David Sankel · CppCon 2017
• 01h 31m“C++ as a "Live at Head" Language”Titus Winters · CppCon 2017
• 45mCongratulations! Legacy Code GURU Level Unlocked!Fernando Cejas · App Builders Switzerland 2019
• 49mContinuous Delivery for Legacy CodeRichard Gross · Build Stuff 2019
• 54mThe Future of the Past – Legacy Will Stay With UsCarola Lilienthal · iSAQB Software Architecture Gathering – Digital 2021
• 58mWho Needs C++ Unit Tests Anyway? - Modernizing Legacy Code with 0% Code CoverageJan Baart · C++ on Sea 2024