cpp-coding-standard

name	cpp-coding-standard
description	C++ coding standard guidelines for names, formatting, and object-oriented design. Use this skill when writing or reviewing C++ code.
license	MIT

C++ Coding Standard

Adapted from http://www.possibility.com/Cpp/CppCodingStandard.html

References

• Resources- Take a Look!
• Names
  • (important recommendations below)
  • Include Units in Names
  • Class Names
  • Class Library Names
  • Method Names
  • Class Attribute Names
  • Method Argument Names
  • C++ File Extensions
  • C Function Names
  • (other suggestions below)
  • Make Names Fit
  • Variable Names on the Stack
  • Pointer Variables
  • Reference Variables and Functions Returning References
  • Global Variables
  • Global Constants
  • Static Variables
  • Type Names
  • Enum Names
  • #define and Macro Names
• Formatting
  • (important recommendations below)
  • Brace {} Policy
  • Parens () with Key Words and Functions Policy
  • A Line Should Not Exceed 78 Characters
  • If Then Else Formatting
  • switch Formatting
  • Use of goto,continue,break and ?:
  • (other suggestions below)
  • One Statement Per Line
  • Alignment of Declaration Blocks
• Classes
  • (important recommendations below)
  • Naming Class Files
  • Class Layout
  • Order of public/protected/private?
  • What should go in public/protected/private?
  • Required Methods for a Class
  • Method Layout
  • Use of Namespaces
  • Use Header File Guards
  • (other suggestions below)
  • Different Accessor Styles
  • Initialize all Variables
  • Think About What Work to do in Constructors
  • Be Careful Throwing Exceptions in Destructors
• Documentation
  • (important recommendations below)
  • Comments Should Tell a Story
  • Document Decisions
  • Use Headers
  • Make Gotchas Explicit
  • Commenting function declarations
  • (other suggestions below)
  • Include Statement Documentation
• Complexity Management
  • Layering
  • Delegation
  • Minimize Dependencies with Abstract Base Classes
  • Liskov's Substitution Principle
  • Follow the Law of Demeter
• Miscellaneous
  • Be Const Correct
  • Use Streams
  • Use #if Not #ifdef
  • Commenting Out Large Code Blocks
  • Don't Over Use Operators
  • Short Methods
  • No Magic Numbers
  • Error Return Check Policy
  • To Use Enums or Not to Use Enums
  • Macros
  • The Bull of Boolean Types
  • Usually Avoid Embedded Assignments
  • Mixing C and C++
  • Miscellaneous
  • No Data Definitions in Header Files
  • Make Functions Reentrant

Source: https://users.ece.cmu.edu/~eno/coding/CppCodingStandard.html