C/C++/COM Coding Guidelines

This page was last updated January 30, 2002

• Hot List - Required Standards
  • Always prefix file with standard copyright notice and revision history
  • Use Standard File Suffixes
  • Each indentation should be a four character tab
  • Indent one level for each new level of logic
  • Align braces with the control statement
  • Put braces on a line by themselves
• Why a Style Guide?
• Document Conventions
• Generic Guidelines
  • File Basics
    • File Names
    • Reasonable Limits
    • Standard File Contents
    • Header Files
  • Formatting
    • White Space
      • Indentation
      • Blank Lines
      • Spaces
    • Code Blocks
    • Statements
      • Continued Statements
  • Comments
  • Declarations and Definitions
    • Naming
      • General naming guidelines
      • Structure, typedef and class names
      • Variable Names
    • Declarations
      • Non-Hardware Dependent Declarations
      • Global Variable Declarations
      • Function Declarations
  • Constants
    • Numeric Literals
    • String Literals
  • Expressions
  • Performance
• C++ Guidelines
  • File Basics
  • Class Specification
    • Member Declaration
    • Constructors
    • Destructors
• COM Guidelines
  • Files