Compiled C++ Coding Standards
summary
A coding standard lives as actual H and CPP files inside the repo so rules compile as code and become searchable, reviewable templates rather than separate markdown. Splash Damage open-sources their files with examples, named tags for easy reference (square tags) and snippets that instantiate into engine actors. A small governance model maintains changes with a core team and ambassadors, CI can auto-format or check some rules, and legacy projects keep the standard as intent while new code follows the live, reviewable rules.
AI-written summary · about
chapters (39)
- 0:00Intro
- 0:45What are coding standards
- 1:11C ISO
- 1:42Core Guidelines
- 2:05C Style Guide
- 2:29AnnieL Engine
- 2:56How Standards Work
- 3:07Standards as Documentation
- 3:44Obstacles
- 4:08Out of date
- 4:46Source code files
- 5:20Visual Studio
- 6:16Source Code
- 6:32H Part
- 7:01Declarations
- 7:58Readability
- 9:18Standard Square Tags
- 9:42Code Reviews
- 10:25Benefits
- 10:55How it grows
- 11:22CPP file
- 11:51CPP layout
- 12:17Epic game style
- 12:40Automation
- 13:09Auto
- 13:19Golden Rule
- 13:40Self calling initialized lambda
- 13:59Disclaimer
- 14:19Lambdas
- 14:57Memory
- 16:23Standest
- 16:41Challenges
- 17:19Open Source
- 17:43Core Team
- 18:12Leadership Team
- 18:25Ambassadors
- 19:13Conclusion
- 19:34Future
- 21:01Quality
related talks
31mDevelopment Standards: A Step-by-Step Guide to Implementing Them Without Pain
01h 06mCore and other guidelines: the good, the bad, the ...questionable?
31mBuilding Consensus on a Set of Rules for Our Massive C++ Codebase
12mWhat are Coding Standards in PHP?
26m(Professionally) Coding with Others
01h 22mHow to Delete Code
53mCode Review Beyond Code Style
25mBest Practices for Writing Clean and Maintainable Codes