October 2004
Intermediate to advanced
240 pages
6h 22m
English
book
C++ Coding Standards: 101 Rules, Guidelines, and Best Practices
by Herb Sutter, Andrei Alexandrescu
Content preview from C++ Coding Standards: 101 Rules, Guidelines, and Best Practices
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
Start your free trial
3. Use a version control system
Summary
The palest of ink is better than the best memory (Chinese proverb): Use a version control system (VCS). Never keep files checked out for long periods. Check in frequently after your updated unit tests pass. Ensure that checked-in code does not break the build.
Discussion
Nearly all nontrivial projects need more than one developer and/or take more than a week of work. On such projects, you will need to compare historical versions of the same file to determine when (and/or by whom) changes were introduced. You will need to control and manage source changes.
When there are multiple developers, those developers will make changes in parallel, possibly to different parts of the same file at the same time. ...