Products
In-IDE
IDE extension that lets you fix coding issues before they exist!
Discover SonarQube for IDE
SaaS
Setup is effortless and analysis is automatic for most languages
Discover SonarQube Cloud
Self-Hosted
Fast, accurate analysis; enterprise scalability
Discover SonarQube Server

Secrets
ABAP
Ansible
Apex
AzureResourceManager
C
C#
C++
CloudFormation
COBOL
CSS
Dart
Docker
Flex
GitHub Actions
Go
HTML
Java
JavaScript
JSON
JCL
Kotlin
Kubernetes
Objective C
PHP
PL/I
PL/SQL
Python
RPG
Ruby
Rust
Scala
Swift
Terraform
Text
TypeScript
T-SQL
VB.NET
VB6
XML
YAML

C++ static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C++ code

Filtered: 51 rules found

misra-c++2008

Impact

Clean code attribute

The name "main" should not be used for any function other than the global "main" function
Code Smell
Pointer and reference parameters should be "const" if the corresponding object is not modified
Code Smell
A variable which is not modified shall be const qualified
Code Smell
"abort", "exit", "getenv" and "system" from <stdlib.h> should not be used
Bug
"offsetof" macro should not be used
Code Smell
There shall be at most one occurrence of the # or ## operators in a single macro definition
Code Smell
In the definition of a function-like macro, each instance of a parameter shall be enclosed in parentheses, unless it is used as the operand of # or ##
Code Smell
#include directives in a file should only be preceded by other preprocessor directives or comments
Code Smell
Functions should not be defined with a variable number of arguments
Code Smell
Evaluation of the operand to the sizeof operator shall not contain side effects
Bug
Switch statement conditions should not have essentially boolean type
Code Smell
The comma operator, "&&", and "||" should not be overloaded
Code Smell
Switch labels should not be nested inside non-switch blocks
Code Smell
A loop-control-variable other than the loop-counter which is modified in statement shall have type bool
Code Smell
The loop-counter should be modified by one of: --, ++, -=n, or +=n; where n remains constant for the duration of the loop
Code Smell
The unary "&" operator should not be overloaded
Code Smell
A cast shall not remove any const or volatile qualification from the type of a pointer or reference
Code Smell
If a function has internal linkage then all re-declarations shall include the static storage class specifer
Code Smell
Objects or functions with external linkage shall be declared in a header file
Code Smell
Functions should not be declared at block scope
Code Smell
The first operand of a conditional operator should have type bool
Code Smell
The condition of an if-statement and the condition of an iteration-statement shall have type bool
Code Smell
Assembly language should be encapsulated and isolated
Code Smell
Each operand of the ! operator, the logical && or the logical || operators shall have type bool
Bug
A cast should not convert a pointer type to an integral type
Code Smell
An object with integral type or pointer to void type shall not be converted to an object with pointer type
Code Smell
An object with pointer type shall not be converted to an unrelated pointer type, either directly or indirectly
Code Smell
The identifiers used for the parameters in a re-declaration or override of a function shall be identical to those in the declaration
Code Smell
using-directives and using-declarations (excluding class scope or function scope using-declarations) shall not be used in header files
Code Smell
A loop-control-variable other than the loop-counter shall not be modified within condition or expression
Code Smell
The loop-counter shall not be modified within condition or statement
Code Smell
If loop-counter is not modified by -- or ++, then, within condition, the loop-counter shall only be used as an operand to <=, <, > or >=
Code Smell
A for loop shall contain a single loop-counter which shall not have floating type
Code Smell
Every switch statement shall have at least one case-clause
Code Smell
All "if ... else if" constructs shall be terminated with an "else "clause
Code Smell
An `if ( condition )` construct shall be followed by a compound statement. The else keyword shall be followed by either a compound statement, or another if statement
Code Smell
The statement forming the body of a "switch", "while", "do {...} while" or "for" statement shall be a compound statement
Code Smell
C-style casts (other than void casts) and functional notation casts (other than explicit constructor calls) shall not be used
Code Smell
A pointer to a virtual base class shall only be cast to a pointer to a derived class by means of dynamic_cast
Bug
When an array is declared, its size shall either be stated explicitly or defined implicitly by initialization
Bug
C libraries should not be used
Code Smell
Destructors should not throw exceptions
Bug
Condition-specific "catch" handlers should not be used after the ellipsis (catch-all) handler
Bug
Handlers in a single try-catch or function-try-block for a derived class and some or all of its bases should be ordered most-derived-first
Bug
Exception classes should be caught by reference
Bug
Handlers of a function-try-block implementation of a class constructor or destructor shall not reference non-static members from this class or its bases
Bug
Control should not be transferred into a complex logic block using a "goto" or a "switch" statement
Code Smell
An exception object should not have pointer type
Bug
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
Code Smell
Multiple declarations for an identifier in the same namespace shall not straddle a using-declaration for that identifier
Bug
Header files should not contain unnamed namespaces
Code Smell

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

intentionality - complete

maintainability

Code Smell

misra-c++2008
suspicious

Why is this an issue?

More Info

This rule is a strict implementation of a MISRA (Motor Industry Software Reliability Association) rule. MISRA defines best practices for developing safety-critical software. You can learn more about this rule in the MISRA documents referenced below.

Available In:

Catch issues on the fly,
in your IDE

Detect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories

Analyze code in your
on-premise CI

Developer Edition
Available Since
9.1

In-IDE

SaaS

Self-Hosted