Our initial set of rules emphasizes safety (of various forms) and simplicity. However, no topic that can help a programmer is out of bounds. We are less concerned with low-level issues, such as naming conventions and indentation style. Such rules affect application architecture and library design.įollowing the rules will lead to code that is statically type safe, has no resource leaks, and catches many more programming logic errors than is common in code today.Īnd it will run fast – you can afford to do things right. The guidelines are focused on relatively high-level issues, such as interfaces, resource management, memory management, and concurrency. In other words, what would you like your code to look like in 5 years’ time, given that you can start now? In 10 years’ time? The aim of this document is to help people to use modern C++ effectively.īy “modern C++” we mean effective use of the ISO C++ standard (currently C++20, but almost all of our recommendations also apply to C++17, C++14 and C++11). This document is a set of guidelines for using C++ well. You can look at design concepts used to express the rules: You can sample rules for specific language features:

FAQ: Answers to frequently asked questions.

You can read an explanation of the scope and structure of this Guide or just jump straight in:

For a more-or-less up-to-date to-do list see: To-do: Unclassified proto-rules.

Update reference sections many pre-C++11 sources are too old.

Triple question marks (?) mark known missing information.

The sets of rules have not been completely checked for completeness, consistency, or enforceability.

When commenting, please note the introduction that outlines our aims and general approach.

We plan to modify and extend this document as our understanding improves and the language and the set of available libraries improve. We make this project available to “friendly users” to use, copy, modify, and derive from, hoping for constructive input.Ĭomments and suggestions for improvements are most welcome. See the accompanying LICENSE file for details. Had it been an open-source (code) project, this would have been release 0.8.Ĭopying, use, modification, and creation of derivative works from this project is licensed under an MIT-style license.Ĭontributing to this project requires agreeing to a Contributor License. This is a living document under continuous improvement.

63 profile human design