SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C++

C++ static code analysis

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

  • All rules 674
  • Vulnerability13
  • Bug139
  • Security Hotspot19
  • Code Smell503

  • Quick Fix 91
Filtered: 17 rules found
misra-advisory
    Impact
      Clean code attribute
        1. The "goto" statement should not be used

           Code Smell
        2. "std::vector" should not be specialized with "bool"

           Code Smell
        3. Variables of array type should not be declared

           Code Smell
        4. "Unscoped enumerations" should not be declared

           Code Smell
        5. Functions with "limited visibility" should be "used" at least once

           Code Smell
        6. All variables should be initialized

           Code Smell
        7. Variables should be captured explicitly in a non-"transient lambda"

           Code Smell
        8. The "#" and "##" preprocessor operators should not be used

           Code Smell
        9. A "noexcept" function should not attempt to propagate an exception to the calling function

           Bug
        10. Classes should not be inherited virtually

           Code Smell
        11. A "declaration" should not declare more than one variable or member variable

           Code Smell
        12. There should be no unnamed namespaces in "header files"

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

           Code Smell
        14. The "declaration" of an object should contain no more than two levels of pointer indirection

           Code Smell
        15. The names of the "standard signed integer types" and "standard unsigned integer types" should not be used

           Code Smell
        16. "#include" directives should only be preceded by preprocessor directives or comments

           Code Smell
        17. Variables with "limited visibility" should be "used" at least once

           Code Smell

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

        consistency - conventional
        maintainability
        Code Smell
        • misra-c++2023
        • misra-advisory

        Why is this an issue?

        More Info

        This rule is part of MISRA C++:2023.

        MISRA Rule 8.2.7

        Category: Advisory

        Analysis Type: Decidable,Single Translation Unit

        Rationale

        Casting between a pointer and an integer type makes it harder for tools and developers to understand and reason about code behaviour. For example, pointer tracking within tools may become unreliable when pointers are cast to integers.

        Note: casting between pointers and integers may be unavoidable when addressing memory mapped registers or other hardware specific features. When the advice given in this rule is not followed, the use of std::uintptr_t or std::intptr_t is required by MISRA C++ 2023 Rule 8.2.8 (An object pointer type shall not be cast to an integral type other than std::uintptr_t or std::intptr_t) as these types are guaranteed to be able to represent all possible pointer values.

        Example

        The following examples violate MISRA C++ 2023 Rule 8.2.8 (An object pointer type shall not be cast to an integral type other than std::uintptr_t or std::intptr_t):

        struct S;
        
        void f( S * s )
        {
          std::intptr_t p = reinterpret_cast< std::intptr_t >( s );   // Non-compliant
          std::uint8_t  q = reinterpret_cast< std::uint8_t  >( s );   // Non-compliant
        }
        

        Copyright The MISRA Consortium Limited © 2023

          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use