MISRA C++:2008 GUIDELINES FOR THE USE

OF THE C++ LANGUAGE IN CRITICAL

SYSTEMS
CODESONAR® 7.1

TRUSTED LEADERS OF SOFTWARE ASSURANCE AND ADVANCED CYBER-SECURITY SOLUTIONS

WWW.GRAMMATECH.COM
1 TECHNICAL
WHITEPAPER
 CODESONAR 7.1 | MISRA C:2012 GUIDELINES FOR THE USE OF THE C/C++ LANGUAGE IN CRITICAL SYSTEMS
(MARCH 2013)

MISRA C++:2008 GUIDELINES FOR THE USE OF THE C++ LANGUAGE IN CRITICAL SYSTEMS

The MISRA C++:2008 standard aims to foster safety, reliability, and portability of programs
written in ISO C for embedded systems. It is used in a wide range of industries, including
automotive, aerospace, medical devices, and industrial control.

CodeSonar 7.1 includes a large number of warning classes that support checking for the MISRA
C++:2008 guidelines. Every CodeSonar warning report includes the numbers of any MISRA
C++:2008 rules and directives that are closely mapped to the warning’s class. (The close
mapping for a warning class is the set of categories—including MISRA C++:2008 rule and
directive numbers—that most closely match the class, if any).

You can configure CodeSonar to enable and disable warning classes mapped to specific MISRA
C++:2008 rules and directives, or use build presets to enable all warning classes that are closely
mapped to any MISRA C++:2008 rules and directives. In addition, you can use the CodeSonar
search function to find warnings related to specific MISRA C++:2008 rules or directives, or to
any MISRA C++:2008 rule or directive.

For more information on MISRA C++:2008:

https://www.misra.org.uk/MISRACHome/tabid/128/Default.aspx

The following table contains CodeSonar classes that are closely mapped to specific
MISRA C++:2008 rules and directives.

Note-All CodeSonar MISRA mappings are close.

Rule Rule Name Supported

MisraC++2008:0-1-1 A project shall not contain unreachable code. Yes
MisraC++2008:0-1-2 A project shall not contain infeasible paths. Yes
MisraC++2008:0-1-3 A project shall not contain unused variables. Yes
MisraC++2008:0-1-4 A project shall not contain non-volatile POD variables having only one use. Yes
MisraC++2008:0-1-5 A project shall not contain unused type declarations. Yes
A project shall not contain instances of non-volatile variables being given values that are never
MisraC++2008:0-1-6 Yes
subsequently used.
The value returned by a function having a non-void return type that is not an overloaded operator
MisraC++2008:0-1-7 Yes
shall always be used.
MisraC++2008:0-1-8 All functions with void return type shall have external side effect(s). Yes
MisraC++2008:0-1-9 There shall be no dead code. Yes
MisraC++2008:0-1-10 Every defined function shall be called at least once. No
MisraC++2008:0-1-11 There shall be no unused parameters (named or unnamed) in non-virtual functions. Yes
There shall be no unused parameters (named or unnamed) in the set of parameters for a virtual
MisraC++2008:0-1-12 Yes
function and all the functions that override it.
MisraC++2008:0-2-1 An object shall not be assigned to an overlapping object. Yes
Minimization of run-time failures shall be ensured by the use of at least one of:(a) static analysis
MisraC++2008:0-3-1 tools/techniques; (b) dynamic analysis tools/techniques; (c) explicit coding of checks to handle run- No
time faults.
MisraC++2008:0-3-2 If a function generates error information, then that error information shall be tested. Yes
MisraC++2008:0-4-1 Use of scaled-integer or fixed-point arithmetic shall be documented. No
MisraC++2008:0-4-2 Use of floating-point arithmetic shall be documented. No
MisraC++2008:0-4-3 Floating-point implementations shall comply with a defined floating-point standard. No

2 TECHNICAL WHITEPAPER
 CODESONAR 7.1 | MISRA C:2012 GUIDELINES FOR THE USE OF THE C/C++ LANGUAGE IN CRITICAL SYSTEMS
(MARCH 2013)

All code shall conform to ISO/IEC 14882:2003 "The C++ Standard Incorporating Technical
MisraC++2008:1-0-1 No
Corrigendum 1."
MisraC++2008:1-0-2 Multiple compilers shall only be used if they have a common, defined interface. No
MisraC++2008:1-0-3 The implementation of integer division in the chosen compiler shall be determined and documented. No
MisraC++2008:2-2-1 The character set and the corresponding encoding shall be documented. No
MisraC++2008:2-3-1 Trigraphs shall not be used. Yes
MisraC++2008:2-5-1 Digraphs should not be used. No
MisraC++2008:2-7-1 The character sequence /* shall not be used within a C-style comment. Yes
MisraC++2008:2-7-2 Sections of code shall not be "commented out" using C-style comments. Yes
MisraC++2008:2-7-3 Sections of code should not be "commented out" using C++ comments. Yes
MisraC++2008:2-10-1 Different identifiers shall be typographically unambiguous. Yes
MisraC++2008:2-10-2 Identifiers declared in an inner scope shall not hide an identifier declared in an outer scope. Yes
MisraC++2008:2-10-3 A typedef name (including qualification, if any) shall be a unique identifier. Yes
MisraC++2008:2-10-4 A class, union or enum name (including qualification, if any) shall be a unique identifier. Yes
The identifier name of a non-member object or function with static storage duration should not be
MisraC++2008:2-10-5 Yes
reused.
MisraC++2008:2-10-6 If an identifier refers to a type, it shall not also refer to an object or a function in the same scope. Yes
MisraC++2008:2-13-1 Only those escape sequences that are defined in ISO/IEC 14882:2003 shall be used. No
MisraC++2008:2-13-2 Octal constants (other than zero) and octal escape sequences (other than "\0") shall not be used. Yes
MisraC++2008:2-13-3 A "U" suffix shall be applied to all octal or hexadecimal integer literals of unsigned type. Yes
MisraC++2008:2-13-4 Literal suffixes shall be upper case. Yes
MisraC++2008:2-13-5 Narrow and wide string literals shall not be concatenated. No
It shall be possible to include any header file in multiple translation units without violating the One
MisraC++2008:3-1-1 Yes
Definition Rule.
MisraC++2008:3-1-2 Functions shall not be declared at block scope. Yes
When an array is declared, its size shall either be stated explicitly or defined implicitly by
MisraC++2008:3-1-3 Yes
initialization.
MisraC++2008:3-2-1 All declarations of an object or function shall have compatible types. Yes
MisraC++2008:3-2-2 The One Definition Rule shall not be violated. Yes
A type, object or function that is used in multiple translation units shall be declared in one and only
MisraC++2008:3-2-3 Yes
one file.
MisraC++2008:3-2-4 An identifier with external linkage shall have exactly one definition. Yes
MisraC++2008:3-3-1 Objects or functions with external linkage shall be declared in a header file. No
If a function has internal linkage then all re-declarations shall include the static storage class
MisraC++2008:3-3-2 No
specifier.
MisraC++2008:3-4-1 An identifier declared to be an object or type shall be defined in a block that minimizes its visibility. Yes
The types used for an object, a function return type, or a function parameter shall be token-for-token
MisraC++2008:3-9-1 Yes
identical in all declarations and re-declarations.
MisraC++2008:3-9-2 typedefs that indicate size and signedness should be used in place of the basic numerical types. Yes
MisraC++2008:3-9-3 The underlying bit representations of floating-point values shall not be used. Yes
Expressions with type bool shall not be used as operands to built-in operators other than the
MisraC++2008:4-5-1 assignment operator = , the logical operators && , || , ! , the equality operators == and != , the unary Yes
& operator, and the conditional operator.
Expressions with type enum shall not be used as operands to built-in operators other than the
MisraC++2008:4-5-2 subscript operator [ ] , the assignment operator = , the equality operators == and != , the unary & Yes
operator, and the relational operators < , <= , > , >= .
Expressions with type (plain) char and wchar_t shall not be used as operands to built-in operators
MisraC++2008:4-5-3 Yes
other than the assignment operator = , the equality operators == and != , and the unary & operator.
MisraC++2008:4-10-1 NULL shall not be used as an integer value. Yes

3 TECHNICAL WHITEPAPER
 CODESONAR 7.1 | MISRA C:2012 GUIDELINES FOR THE USE OF THE C/C++ LANGUAGE IN CRITICAL SYSTEMS
(MARCH 2013)

MisraC++2008:4-10-2 Literal zero (0) shall not be used as the null-pointer-constant. Yes
The value of an expression shall be the same under any order of evaluation that the standard
MisraC++2008:5-0-1 No
permits.
MisraC++2008:5-0-2 Limited dependence should be placed on C++ operator precedence rules in expressions. Yes
MisraC++2008:5-0-3 A cvalue expression shall not be implicitly converted to a different underlying type. Yes
MisraC++2008:5-0-4 An implicit integral conversion shall not change the signedness of the underlying type. Yes
MisraC++2008:5-0-5 There shall be no implicit floating-integral conversions. Yes
MisraC++2008:5-0-6 An implicit integral or floating-point conversion shall not reduce the size of the underlying type. Yes
MisraC++2008:5-0-7 There shall be no explicit floating-integral conversions of a cvalue expression. Yes
An explicit integral or floating-point conversion shall not increase the size of the underlying type of
MisraC++2008:5-0-8 Yes
a cvalue expression.
An explicit integral conversion shall not change the signedness of the underlying type of a cvalue
MisraC++2008:5-0-9 Yes
expression.
If the bitwise operators ~ and << are applied to an operand with an underlying type of unsigned char
MisraC++2008:5-0-10 Yes
or unsigned short, the result shall be immediately cast to the underlying type of the operand.
MisraC++2008:5-0-11 The plain char type shall only be used for the storage and use of character values. Yes
MisraC++2008:5-0-12 signed char and unsigned char type shall only be used for the storage and use of numeric values. Yes
MisraC++2008:5-0-13 The condition of an if-statement and the condition of an iteration-statement shall have type bool. Yes
MisraC++2008:5-0-14 The first operand of a conditional-operator shall have type bool. Yes
MisraC++2008:5-0-15 Array indexing shall be the only form of pointer arithmetic. Yes
A pointer operand and any pointer resulting from pointer arithmetic using that operand shall both
MisraC++2008:5-0-16 Yes
address elements of the same array.
Subtraction between pointers shall only be applied to pointers that address elements of the same
MisraC++2008:5-0-17 Yes
array.
> , >= , < , <= shall not be applied to objects of pointer type, except where they point to the same
MisraC++2008:5-0-18 Yes
array.
MisraC++2008:5-0-19 The declaration of objects shall contain no more than two levels of pointer indirection. Yes
MisraC++2008:5-0-20 Non-constant operands to a binary bitwise operator shall have the same underlying type. Yes
MisraC++2008:5-0-21 Bitwise operators shall only be applied to operands of unsigned underlying type. Yes
MisraC++2008:5-2-1 Each operand of a logical && or || shall be a postfix-expression. No
A pointer to a virtual base class shall only be cast to a pointer to a derived class by means of
MisraC++2008:5-2-2 Yes
dynamic_cast.
MisraC++2008:5-2-3 Casts from a base class to a derived class should not be performed on polymorphic types. No
C-style casts (other than void casts) and functional notation casts (other than explicit constructor
MisraC++2008:5-2-4 Yes
calls) shall not be used.
MisraC++2008:5-2-5 A cast shall not remove any const or volatile qualification from the type of a pointer or reference. Yes
A cast shall not convert a pointer to a function to any other pointer type, including a pointer to
MisraC++2008:5-2-6 Yes
function type.
An object with pointer type shall not be converted to an unrelated pointer type, either directly or
MisraC++2008:5-2-7 Yes
indirectly.
An object with integer type or pointer to void type shall not be converted to an object with pointer
MisraC++2008:5-2-8 Yes
type.
MisraC++2008:5-2-9 A cast should not convert a pointer type to an integral type. Yes
The increment ( ++ ) and decrement ( -- ) operators should not be mixed with other operators in an
MisraC++2008:5-2-10 Yes
expression.
MisraC++2008:5-2-11 The comma operator, && operator and the || operator shall not be overloaded. Yes
MisraC++2008:5-2-12 An identifier with array type passed as a function argument shall not decay to a pointer. Yes
MisraC++2008:5-3-1 Each operand of the ! operator, the logical && or the logical || operators shall have type bool. Yes
MisraC++2008:5-3-2 The unary minus operator shall not be applied to an expression whose underlying type is unsigned. Yes
MisraC++2008:5-3-3 The unary & operator shall not be overloaded. Yes

4 TECHNICAL WHITEPAPER
 CODESONAR 7.1 | MISRA C:2012 GUIDELINES FOR THE USE OF THE C/C++ LANGUAGE IN CRITICAL SYSTEMS
(MARCH 2013)

MisraC++2008:5-3-4 Evaluation of the operand to the sizeof operator shall not contain side effects. Yes
The right hand operand of a shift operator shall lie between zero and one less than the width in bits
MisraC++2008:5-8-1 Yes
of the underlying type of the left hand operand.
MisraC++2008:5-14-1 The right hand operand of a logical && or || operator shall not contain side effects. Yes
The semantic equivalence between a binary operator and its assignment operator form shall be
MisraC++2008:5-17-1 No
preserved.
MisraC++2008:5-18-1 The comma operator shall not be used. Yes
MisraC++2008:5-19-1 Evaluation of constant unsigned integer expressions should not lead to wrap-around. No
MisraC++2008:6-2-1 Assignment operators shall not be used in sub-expressions. Yes
MisraC++2008:6-2-2 Floating-point expressions shall not be directly or indirectly tested for equality or inequality. Yes
Before preprocessing, a null statement shall only occur on a line ny itself; it may be followed by a
MisraC++2008:6-2-3 No
comment, provided that the first character following the null statement is a white-space character.
The statement forming the body of a switch, while, do ... while or for statement shall be a compound
MisraC++2008:6-3-1 Yes
statement.
An if ( condition ) construct shall be followed by a compound statement. The else keyword shall be
MisraC++2008:6-4-1 Yes
followed by either a compound statement, or another if statement.
MisraC++2008:6-4-2 All if ... else if constructs shall be terminated with an else clause. Yes
MisraC++2008:6-4-3 A switch statement shall be a well-formed switch statement. Yes
A switch-label shall only be used when the most closely-enclosing compound statement is the body
MisraC++2008:6-4-4 Yes
of a switch statement.
MisraC++2008:6-4-5 An unconditional throw or break statement shall terminate every non-empty switch-clause. Yes
MisraC++2008:6-4-6 The final clause of a switch statement shall be the default-clause. Yes
MisraC++2008:6-4-7 The condition of a switch statement shall not have bool type. Yes
MisraC++2008:6-4-8 Every switch statement shall have at least one case-clause. Yes
MisraC++2008:6-5-1 A for loop shall contain a single loop-counter which shall not have floating type. Yes
If loop-counter is not modified by -- or ++ , then, within condition, the loop-counter shall only be
MisraC++2008:6-5-2 No
used as an operand to <= , < , > or >= .
MisraC++2008:6-5-3 The loop-counter shall not be modified within condition or statement. Yes
The loop-counter shall be modified by one of -- , ++ , -=n , or +=n; where n remains constant for the
MisraC++2008:6-5-4 Yes
duration of the loop.
A loop-control-variable other than the loop-counter shall not be modified within condition or
MisraC++2008:6-5-5 Yes
expression.
A loop-control-variable other than the loop-counter which is modified in statement shall have type
MisraC++2008:6-5-6 No
bool.
Any label referenced by a goto statement shall be declared in the same block, or in a block enclosing
MisraC++2008:6-6-1 Yes
the goto statement.
MisraC++2008:6-6-2 The goto statement shall jump to a label declared later in the same function body. Yes
MisraC++2008:6-6-3 The continue statement shall only be used within a well-formed for loop. Yes
For any iteration statement there shall be no more than one break or goto statement used for loop
MisraC++2008:6-6-4 Yes
termination.
MisraC++2008:6-6-5 A function shall have a single point of exit at the end of the function. Yes
MisraC++2008:7-1-1 A variable which is not modified shall be const qualified. Yes
A pointer or reference parameter in a function shall be declared as pointer to const or reference to
MisraC++2008:7-1-2 Yes
const if the corresponding object is not modified.
An expression with enum underlying type shall only have values corresponding to the enumerators
MisraC++2008:7-2-1 Yes
of the enumeration.
MisraC++2008:7-3-1 The global namespace shall only contain main, namespace declarations and extern "C" declarations. Yes
MisraC++2008:7-3-2 The identifier main shall not be used for a function other than the global function main. No
MisraC++2008:7-3-3 There shall be no unnamed namespaces in header files. Yes
MisraC++2008:7-3-4 using-directives shall not be used. Yes

5 TECHNICAL WHITEPAPER
 CODESONAR 7.1 | MISRA C:2012 GUIDELINES FOR THE USE OF THE C/C++ LANGUAGE IN CRITICAL SYSTEMS
(MARCH 2013)

Multiple declarations for an identifier in the same namespace shall not straddle a using-declaration
MisraC++2008:7-3-5 Yes
for that identifier.
using-directives and using-declarations (excluding class scope or function scope using-declarations)
MisraC++2008:7-3-6 Yes
shall not be used in header files.
MisraC++2008:7-4-1 All usage of assembler shall be documented. No
MisraC++2008:7-4-2 Assembler instructions shall only be introduced using the asm declaration. Yes
MisraC++2008:7-4-3 Assembly language shall be encapsulated and isolated. Yes
A function shall not return a reference or a pointer to an automatic variable (including parameters),
MisraC++2008:7-5-1 Yes
defined within the function.
The address of an object with automatic storage shall not be assigned to another object that may
MisraC++2008:7-5-2 Yes
persist afer the first object has ceased to exist.
A function shall not return a reference or a pointer to a parameter that is passed by reference or
MisraC++2008:7-5-3 No
const reference.
MisraC++2008:7-5-4 Functions should not call themselves, either directly or indirectly. Yes
An init-declarator-list or a member-declarator-list shall consist of a single init-declarator or
MisraC++2008:8-0-1 No
member-declarator respectively.
Parameters in an overriding virtual function shall either use the same default arguments as the
MisraC++2008:8-3-1 Yes
function they override, or else shall not specify any default arguments.
MisraC++2008:8-4-1 Functions shall not be defined using the ellipsis notation. Yes
The identifiers used for the parameters in a re-declaration of a function shall be identical to those in
MisraC++2008:8-4-2 Yes
the declaration.
All exit paths from a function with non-void return type shall have an explicit return statement with
MisraC++2008:8-4-3 Yes
an expression.
MisraC++2008:8-4-4 A function identifier shall either be used to call the function or it shall be preceded by &. Yes
MisraC++2008:8-5-1 All variables shall have a defined value before they are used. Yes
Braces shall be used to indicate and match the structure in the non-zero initialization of arrays and
MisraC++2008:8-5-2 Yes
structures.
In an enumerator list, the = construct shall not be used to explicitly initialize members other than the
MisraC++2008:8-5-3 Yes
first, unless all items are explicitly initialized.
MisraC++2008:9-3-1 const member functions shall not return non-const pointers or references to class-data. No
MisraC++2008:9-3-2 Member functions shall not return non-const handles to class-data. No
If a member function can be made static then it shall be made static, otherwise if it can be made
MisraC++2008:9-3-3 Yes
const then it shall be made const.
MisraC++2008:9-5-1 Unions shall not be used. Yes
When the absolute partitioning of bits representing a bit-field is required, then the behaviour and
MisraC++2008:9-6-1 No
packing of bit-fields shall be documented.
MisraC++2008:9-6-2 Bit-fields shall be either bool type or an explicitly unsigned or signed integral type. Yes
MisraC++2008:9-6-3 Bit-fields shall not have enum type. Yes
MisraC++2008:9-6-4 Named bit-fields with signed integer type shall have a length of more than one bit. Yes
MisraC++2008:10-1-1 Classes should not be derived from virtual bases. Yes
MisraC++2008:10-1-2 A base class shall only be declared virtual if it is used in a diamond hierarchy. Yes
MisraC++2008:10-1-3 An accessible base class shall not be both virtual and non-virtual in the same hierarchy. Yes
MisraC++2008:10-2-1 All accessible entity names within a multiple inheritance hierarchy should be unique. No
There shall be no more than one definition of each virtual function on each path through the
MisraC++2008:10-3-1 No
inheritance hierarchy.
MisraC++2008:10-3-2 Each overriding virtual function shall be declared with the virtual keyword. No
A virtual function shall only be overridden by a pure virtual function if it is itself declared as pure
MisraC++2008:10-3-3 No
virtual.
MisraC++2008:11-0-1 Member data in non-POD class types shall be private. No
MisraC++2008:12-1-1 An object's dynamic type shall not be used from the body of its constructor or destructor. Yes

6 TECHNICAL WHITEPAPER
 CODESONAR 7.1 | MISRA C:2012 GUIDELINES FOR THE USE OF THE C/C++ LANGUAGE IN CRITICAL SYSTEMS
(MARCH 2013)

All constructors of a class should explicitly call a constructor for all of its immediate base classes
MisraC++2008:12-1-2 No
and all virtual base classes.
All constructors that are callable with a single argument of fundamental type shall be declared
MisraC++2008:12-1-3 No
explicit.
A copy constructor shall only initialize its base classes and the non- static members of the class of
MisraC++2008:12-8-1 Yes
which it is a member.
MisraC++2008:12-8-2 The copy assignment operator shall be declared protected or private in an abstract class. Yes
A non-member generic function shall only be declared in a namespace that is not an associated
MisraC++2008:14-5-1 No
namespace.
A copy constructor shall be declared when there is a template constructor with a single parameter
MisraC++2008:14-5-2 No
that is a generic parameter.
A copy assignment operator shall be declared when there is a template assignment operator with a
MisraC++2008:14-5-3 No
parameter that is a generic parameter.
In a class template with a dependent base, any name that may be found in that dependent base shall
MisraC++2008:14-6-1 No
be referred to using a qualified-id or this->
The function chosen by overload resolution shall resolve to a function declared previously in the
MisraC++2008:14-6-2 No
translation unit.
All class templates, function templates, class template member functions and class template static
MisraC++2008:14-7-1 No
members shall be instantiated at least once.
For any given template specialization, an explicit instantiation of the template with the template-
MisraC++2008:14-7-2 No
arguments used in the specialization shall not render the program ill-formed.
All partial and explicit specializations for a template shall be declared in the same file as the
MisraC++2008:14-7-3 No
declaration of their primary template.
MisraC++2008:14-8-1 Overloaded function templates shall not be explicitly specialized. No
The viable function set for a function call should either contain no function specializations, or only
MisraC++2008:14-8-2 No
contain function specializations.
MisraC++2008:15-0-1 Exceptions shall only be used for error handling. No
MisraC++2008:15-0-2 An exception object should not have pointer type. No
MisraC++2008:15-0-3 Control shall not be transferred into a try or catch block using a goto or a switch statement. No
MisraC++2008:15-1-1 The assignment-expression of a throw statement shall not itself cause an exception to be thrown. No
MisraC++2008:15-1-2 NULL shall not be thrown explicitly. No
MisraC++2008:15-1-3 An empty throw ( throw; ) shall only be used in the compound- statement of a catch handler. No
MisraC++2008:15-3-1 Exceptions shall be raised only after start-up and before termination of the program. No
MisraC++2008:15-3-2 There should be at least one exception handler to catch all otherwise unhandled exceptions. No
Handlers of a function-try-block implementation of a class constructor or destructor shall not
MisraC++2008:15-3-3 No
reference non-static members from this class or its bases.
Each exception explicitly thrown in the code shall have a handler of a compatible type in all call
MisraC++2008:15-3-4 No
paths that could lead to that point.
MisraC++2008:15-3-5 A class type exception shall always be caught by reference. Yes
Where multiple handlers are provided in a single try-catch statement or function-try-block for a
MisraC++2008:15-3-6 Yes
derived class and some or all of its bases, the handlers shall be ordered most-derived to base class.
Where multiple handlers are provided in a single try-catch statement or function-try-block, any
MisraC++2008:15-3-7 Yes
ellipsis (catch-all) handler shall occur last.
If a function is declared with an exception-specification, then all declarations of the same function
MisraC++2008:15-4-1 No
(in other translation units) shall be declared with the same set of type-ids.
MisraC++2008:15-5-1 A class destructor shall not exit with an exception. No
Where a function's declaration includes an exception-specification, the function shall only be
MisraC++2008:15-5-2 No
capable of throwing exceptions of the indicated type(s).
MisraC++2008:15-5-3 The terminate() function shall not be called implicitly. No
MisraC++2008:16-0-1 #include directives in a file shall only be preceded by preprocessor directives or comments. Yes
MisraC++2008:16-0-2 Macros shall only be #define'd or #undef'd in the global namespace. No

7 TECHNICAL WHITEPAPER
 CODESONAR 7.1 | MISRA C:2012 GUIDELINES FOR THE USE OF THE C/C++ LANGUAGE IN CRITICAL SYSTEMS
(MARCH 2013)

MisraC++2008:16-0-3 #undef shall not be used. Yes

MisraC++2008:16-0-4 Function-like macros shall not be defined. Yes
MisraC++2008:16-0-5 Arguments to a function-like macro shall not contain tokens that look like preprocessing directives. Yes
In the definition of a function-like macro, each instance of a parameter shall be enclosed in
MisraC++2008:16-0-6 Yes
parentheses, unless it is used as the operand of # or ## .
Undefined macro identifiers shall not be used in #if or #elif preprocessor directives, except as
MisraC++2008:16-0-7 Yes
operands to the defined operator.
If the # token appears as the first token on a line, then it shall be immediately followed by a
MisraC++2008:16-0-8 Yes
preprocessing token.
MisraC++2008:16-1-1 The defined preprocessor operator shall only be used in one of the two standard forms. No
All #else, #elif and #endif preprocessor directives shall reside in the same file as the #if or #ifdef
MisraC++2008:16-1-2 Yes
directive to which they are related.
MisraC++2008:16-2-1 The pre-processor shall only be used for file inclusion and include guards. No
MisraC++2008:16-2-2 C++ macros shall only be used for include guards, type qualifiers, or storage class specifiers. No
MisraC++2008:16-2-3 Include guards shall be provided. No
MisraC++2008:16-2-4 The ', ", /* or // characters shall not occur in a header file name. Yes
MisraC++2008:16-2-5 The \ character should not occur in a header file name. Yes
MisraC++2008:16-2-6 The #include directive shall be followed by either a or "filename" sequence. Yes
MisraC++2008:16-3-1 There shall be at most one occurrence of the # or ## operators in a single macro definition. No
MisraC++2008:16-3-2 The # and ## operators should not be used. Yes
MisraC++2008:16-6-1 All uses of the #pragma directive shall be documented. No
Reserved identifiers, macros and functions in the standard library shall not be defined, redefined or
MisraC++2008:17-0-1 Yes
undefined.
MisraC++2008:17-0-2 The names of standard library macros and objects shall not be reused. Yes
MisraC++2008:17-0-3 The names of standard library functions shall not be overridden. Yes
MisraC++2008:17-0-4 All library code shall conform to MISRA C++. No
MisraC++2008:17-0-5 The setjmp macro and the longjmp function shall not be used. Yes
MisraC++2008:18-0-1 The C library shall not be used. Yes
MisraC++2008:18-0-2 The library functions atof, atoi and atol from library shall not be used. Yes
MisraC++2008:18-0-3 The library functions abort, exit, getenv and system from library shall not be used. Yes
MisraC++2008:18-0-4 The time handling functions of library shall not be used. Yes
MisraC++2008:18-0-5 The unbounded functions of library shall not be used. Yes
MisraC++2008:18-2-1 The macro offsetof shall not be used. Yes
MisraC++2008:18-4-1 Dynamic heap memory allocation shall not be used. Yes
MisraC++2008:18-7-1 The signal handling facilities of shall not be used. Yes
MisraC++2008:19-3-1 The error indicator errno shall not be used. No
MisraC++2008:27-0-1 The stream input/output library shall not be used. Yes

GrammaTech is a leading global provider of application testing (AST) solutions used by the
world’s most security conscious organizations to detect, measure, analyze and resolve
vulnerabilities for software they develop or use. The company is also a trusted cybersecurity
and artificial intelligence research partner for the nation’s civil, defense, and intelligence
agencies.

CodeSonar and CodeSentry are registered trademarks of GrammaTech, Inc.

© GrammaTech, Inc. All rights reserved.

8 TECHNICAL WHITEPAPER