0.1.1

A project shall not contain unreachable code.

Required

Yes

0.1.3

A project shall not contain unused variables.

Required

Yes

0.1.5

A project shall not contain unused type declarations.

Required

Yes

0.1.7

The value returned by a function having a non-void return type that is not an overloaded operator shall always be used.

Required

Yes

0.1.9

There shall be no dead code.

Required

Yes

0.1.11

There shall be no unused parameters (named or unnamed) in non-virtual functions.

Required

Yes

0.2.1

An object shall not be assigned to an overlapping object.

Required

Yes

1.0.1

All code shall conform to ISO/IEC 14882:2003 “The C++ Standard Incorporating Technical Corrigendum 1”.

Required

Yes

2.5.1

Digraphs should not be used.

Advisory

Yes

2.7.2

Sections of code shall not be “commented out” using C-style comments.

Required

Yes

2.10.1

Different identifiers shall be typographically unambiguous.

Required

Yes

2.10.3

A typedef name (including qualification, if any) shall be a unique identifier.

Required

Yes

2.10.5

The identifier name of a non-member object or function with static storage duration should not be reused.

Advisory

Yes

2.13.1

Only those escape sequences that are defined in ISO/IEC 14882:2003 shall be used.

Required

Yes

2.13.3

A “U” suffix shall be applied to all octal and all hexadecimal integer literals of unsigned type.

Required

Yes

2.13.5

Narrow and wide string literals shall not be concatenated.

Required

Yes

3.1.2

Functions shall not be declared at block scope.

Required

Yes

3.2.1

All declarations of an object or function shall have compatible types.

Required

Yes

3.2.3

A type, object or function that is used in multiple translation units shall be declared in one and only one file.

Required

Yes

3.3.1

Objects or functions with external linkage shall be declared in a header file.

Required

Yes

3.4.1

An identifier declared to be an object or type shall be defined in a block that minimizes its visibility.

Required

Yes

3.9.2

typedefs that indicate size and signedness should be used in place of the basic numerical types.

Advisory

Yes

4.5.1

Expressions with type bool shall not be used as operands to built-in operators other than the assignment operator =, the logical operators &&, ||, !, the equality operators == and !=, the unary & operator, and the conditional operator.

Required

Yes

4.5.3

Expressions with type (plain) char and wchar_t shall not be used as operands to built-in operators other than the assignment operator =, the equality operators == and !=, and the unary & operator.

Required

Yes

4.10.2

Literal zero (0) shall not be used as the null-pointer-constant.

Required

Yes

5.0.2

Limited dependence should be placed on C++ operator precedence rules in expressions.

Advisory

Yes

5.0.4

An implicit integral conversion shall not change the signedness of the underlying type.

Required

Yes

5.0.6

An implicit integral or floating-point conversion shall not reduce the size of the underlying type.

Required

Yes

5.0.8

An explicit integral or floating-point conversion shall not increase the size of the underlying type of a cvalue expression.

Required

Yes

5.0.10

If the bitwise operators ~ and « are applied to an operand with an underlying type of unsigned char or unsigned short, the result shall be immediately cast to the underlying type of the operand.

Required

Yes

5.0.12

signed char and unsigned char type shall only be used for the storage and use of numeric values.

Required

Yes

5.0.14

The first operand of a conditional-operator shall have type bool.

Required

Yes

5.0.16

A pointer operand and any pointer resulting from pointer arithmetic using that operand shall both address elements of the same array.

Required

Yes

5.0.18

>, >=, <, ← shall not be applied to objects of pointer type, except where they point to the same array.

Required

Yes

5.0.20

Non-constant operands to a binary bitwise operator shall have the same underlying type.

Required

Yes

5.2.1

Each operand of a logical && or || shall be a postfix expression.

Required

Yes

5.2.3

Casts from a base class to a derived class should not be performed on polymorphic types.

Advisory

Yes

5.2.5

A cast shall not remove any const or volatile qualification from the type of a pointer or reference.

Required

Yes

5.2.7

An object with pointer type shall not be converted to an unrelated pointer type, either directly or indirectly.

Required

Yes

5.2.9

A cast should not convert a pointer type to an integral type.

Advisory

Yes

5.2.11

The comma operator, && operator and the || operator shall not be overloaded.

Required

Yes

5.3.1

Each operand of the ! operator, the logical && or the logical || operators shall have type bool.

Required

Yes

5.3.3

The unary & operator shall not be overloaded.

Required

Yes

5.8.1

The right hand operand of a shift operator shall lie between zero and one less than the width in bits of the underlying type of the left hand operand.

Required

Yes

5.17.1

The semantic equivalence between a binary operator and its assignment operator form shall be preserved.

Required

Yes

5.19.1

Evaluation of constant unsigned integer expressions should not lead to wrap-around.

Advisory

Yes

6.2.2

Floating-point expressions shall not be directly or indirectly tested for equality or inequality.

Required

Yes

6.3.1

The statement forming the body of a switch, while, do … while or for statement shall be a compound statement.

Required

Yes

6.4.2

All if … else if constructs shall be terminated with an else clause.

Required

Yes

6.4.4

A switch-label shall only be used when the most closely-enclosing compound statement is the body of a switch statement.

Required

Yes

6.4.6

The final clause of a switch statement shall be the default-clause.

Required

Yes

6.4.8

Every switch statement shall have at least one case-clause.

Required

Yes

6.5.2

If loop-counter is not modified by – or ++, then, within condition, the loop-counter shall only be used as an operand to ←, <, > or >=.

Required

Yes

6.5.4

The loop-counter shall be modified by one of: –, ++, -=n, or +=n; where n remains constant for the duration of the loop.

Required

Yes

6.5.6

A loop-control-variable other than the loop-counter which is modified in statement shall have type bool.

Required

Yes

6.6.2

The goto statement shall jump to a label declared later in the same function body.

Required

Yes

6.6.4

For any iteration statement there shall be no more than one break or goto statement used for loop termination.

Required

Yes

7.1.1

A variable which is not modified shall be const qualified.

Required

Yes

7.2.1

An expression with enum underlying type shall only have values corresponding to the enumerators of the enumeration.

Required

Yes

7.3.2

The identifier main shall not be used for a function other than the global function main.

Required

Yes

7.3.4

using-directives shall not be used.

Required

Yes

7.3.6

using-directives and using-declarations (excluding class scope or function scope using-declarations) shall not be used in header files.

Required

Yes

7.4.3

Assembly language shall be encapsulated and isolated.

Required

Yes

7.5.2

The address of an object with automatic storage shall not be assigned to another object that may persist after the first object has ceased to exist.

Required

Yes

7.5.4

Functions should not call themselves, either directly or indirectly.

Advisory

Yes

8.3.1

Parameters in an overriding virtual function shall either use the same default arguments as the function they override, or else shall not specify any default arguments.

Required

Yes

8.4.2

The identifiers used for the parameters in a re-declaration or override of a function shall be identical to those in the declaration.

Required

Yes

8.4.4

A function identifier shall either be used to call the function or it shall be preceded by &.

Required

Yes

8.5.2

Braces shall be used to indicate and match the structure in the non-zero initialization of arrays and structures.

Required

Yes

9.3.1

const member functions shall not return non-const pointers or references to class-data.

Required

Yes

9.3.3

If a member function can be made static then it shall be made static, otherwise if it can be made const then it shall be made const.

Required

Yes

9.6.2

Bit-fields shall be either bool type or an explicitly unsigned or signed integral type.

Required

Yes

9.6.4

Named bit-fields with signed integer type shall have a length of more than one bit.

Required

Yes

10.1.2

A base class shall only be declared virtual if it is used in a diamond hierarchy.

Required

Yes

10.2.1

All accessible entity names within a multiple inheritance hierarchy should be unique.

Advisory

Yes

10.3.2

Each overriding virtual function shall be declared with the virtual keyword.

Required

Yes

11.0.1

Member data in non-POD class types shall be private.

Required

Yes

12.1.2

All constructors of a class should explicitly call a constructor for all of its immediate base classes and all virtual base classes.

Advisory

Yes

12.8.1

A copy constructor shall only initialize its base classes and the non-static members of the class of which it is a member.

Required

Yes

14.5.1

A non-member generic function shall only be declared in a namespace that is not an associated namespace.

Required

Yes

14.5.3

A copy assignment operator shall be declared when there is a template assignment operator with a parameter that is a generic parameter.

Required

Yes

14.6.2

The function chosen by overload resolution shall resolve to a function declared previously in the translation unit.

Required

Yes

14.7.2

For any given template specialization, an explicit instantiation of the template with the template-arguments used in the specialization shall not render the program ill-formed.

Required

No

14.8.1

Overloaded function templates shall not be explicitly specialized.

Required

Yes

15.0.2

An exception object should not have pointer type.

Advisory

Yes

15.1.1

The assignment-expression of a throw statement shall not itself cause an exception to be thrown.

Required

Yes

15.1.3

An empty throw (throw;) shall only be used in the compound-statement of a catch handler.

Required

Yes

15.3.2

There should be at least one exception handler to catch all otherwise unhandled exceptions.

Advisory

Yes

15.3.4

Each exception explicitly thrown in the code shall have a handler of a compatible type in all call paths that could lead to that point.

Required

Yes

15.3.6

Where multiple handlers are provided in a single try-catch statement or function-try-block for a derived class and some or all of its bases, the handlers shall be ordered most-derived to base class.

Required

Yes

15.4.1

If a function is declared with an exception-specification, then all declarations of the same function (in other translation units) shall be declared with the same set of type-ids.

Required

Yes

15.5.2

Where a function’s declaration includes an exception-specification, the function shall only be capable of throwing exceptions of the indicated type(s).

Required

Yes

16.0.1

#include directives in a file shall only be preceded by other preprocessor directives or comments.

Required

Yes

16.0.3

#undef shall not be used.

Required

Yes

16.0.5

Arguments to a function-like macro shall not contain tokens that look like preprocessing directives.

Required

Yes

16.0.7

Undefined macro identifiers shall not be used in #if or #elif preprocessor directives, except as operands to the defined operator.

Required

Yes

16.1.1

The defined preprocessor operator shall only be used in one of the two standard forms.

Required

Yes

16.2.1

The pre-processor shall only be used for file inclusion and include guards.

Required

Yes

16.2.3

Include guards shall be provided.

Required

Yes

16.2.5

The \ character should not occur in a header file name.

Advisory

Yes

16.3.1

There shall be at most one occurrence of the # or ## operators in a single macro definition.

Required

Yes

17.0.1

Reserved identifiers, macros and functions in the standard library shall not be defined, redefined or undefined.

Required

Yes

17.0.3

The names of standard library functions shall not be overridden.

Required

Yes

18.0.1

The C library shall not be used.

Required

Yes

18.0.3

The library functions abort, exit, getenv and system from library  shall not be used.

Required

Yes

18.0.5

The unbounded functions of library  shall not be used.

Required

Yes

18.4.1

Dynamic heap memory allocation shall not be used.

Required

Yes

19.3.1

The error indicator errno shall not be used.

Required

Yes

0.3.1

Minimization of run-time failures shall be ensured by the use of at least one of: (a) static analysis tools/techniques; (b) dynamic analysis tools/techniques; © explicit coding of checks to handle run-time faults.

Document

Assisted

0.4.2

Use of floating-point arithmetic shall be documented.

Document

Assisted

1.0.2

Multiple compilers shall only be used if they have a common, defined interface.

Document

Unassisted

2.2.1

The character set and the corresponding encoding shall be documented.

Document

Unassisted

9.6.1

When the absolute positioning of bits representing a bit-field is required, then the behaviour and packing of bit-fields shall be documented.

Document

Unassisted

16.6.1

All uses of the #pragma directive shall be documented.

Document

Assisted