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 798
  • Vulnerability14
  • Bug173
  • Security Hotspot19
  • Code Smell592

  • Quick Fix 99
Filtered: 35 rules found
unused
    Impact
      Clean code attribute
        1. Non-empty statements should change control flow or have at least one side-effect

           Bug
        2. Unused type declarations should be removed

           Code Smell
        3. Calls to "std::format" with a locale should use the "L" flag

           Code Smell
        4. "std::format" should not have unused arguments

           Code Smell
        5. "std::format" should not be missing indexes

           Bug
        6. Width, alignment, and padding format options should be used consistently

           Code Smell
        7. Functions that are not used in a project should be removed

           Code Smell
        8. "extern" shouldn't be used on member definitions

           Bug
        9. Reference types should not be qualified with "const" or "volatile"

           Code Smell
        10. Namespaces should not be empty

           Code Smell
        11. Forward declarations should not be redundant

           Code Smell
        12. Declarations should not be empty

           Code Smell
        13. "catch" clauses should do more than rethrow

           Code Smell
        14. Conditionally executed code should be reachable

           Bug
        15. Values should not be uselessly incremented

           Bug
        16. Related "if/else if" statements should not have the same condition

           Bug
        17. Unused assignments should be removed

           Code Smell
        18. All code should be reachable

           Bug
        19. Unused local variables should be removed

           Code Smell
        20. Sections of code should not be commented out

           Code Smell
        21. Unused function parameters should be removed

           Code Smell
        22. Unused functions and methods should be removed

           Code Smell
        23. Empty statements should be removed

           Code Smell
        24. Unused "private" fields should be removed

           Code Smell
        25. Unused labels should be removed

           Code Smell
        26. Condition-specific "catch" handlers should not be used after the ellipsis (catch-all) handler

           Bug
        27. Functions with "limited visibility" should be "used" at least once

           Code Smell
        28. Sections of code should not be "commented out"

           Code Smell
        29. A named function parameter shall be "used" at least once

           Code Smell
        30. The value returned by a function shall be "used"

           Code Smell
        31. A value should not be "unnecessarily written" to a local object

           Code Smell
        32. Types with "limited visibility" should be "used" at least once

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

           Code Smell
        34. Controlling expressions should not be invariant

           Bug
        35. A function shall not contain "unreachable" statements

           Bug

        Sections of code should not be "commented out"

        intentionality - clear
        maintainability
        Code Smell
        • unused
        • misra-c++2023
        • misra-advisory
        • misra-directive

        Why is this an issue?

        More Info

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

        Usage of this content is governed by Sonar’s terms and conditions. Redistribution is prohibited.

        Dir 5.7.2 - Sections of code should not be "commented out"

        Category: Advisory

        Amplification

        This directive applies to the use of both // and /* ... */ style comments.

        For the purposes of this directive, the use of #if 0 is also considered to be "commenting out".

        Rationale

        Comments should only be used to explain aspects of the source code; they should not be used to record the history of changes to the source code.

        In addition, whilst the nesting of C-style comments is not supported by the C++ Standard, it is supported by some compilers. This means that the commenting out of any code that contains comments may behave differently with different compilers (see M23_025: MISRA C++ 2023 Rule 5.7.1).

        This directive is generally undecidable, as it is not always possible for a tool to determine if a comment contains explanatory text, a code example or commented out code.

        Note: it is acknowledged that it may be useful to quote statements or expressions as part of a larger comment in order to document and explain some aspect of the program (e.g. clarifying the use of a function, or explaining the algorithm being implemented). Such usage is not the intended target of this directive.

        Example

        The following compliant example documents an API with the use of pseudo-code. It is assumed that code wrapped within the ``` markup is recognized as documentation and is not commented out code.

        // You should not call lock/unlock directly, but through RAII:
        // ```
        //   void f( Data & d, MyMutex & m )
        //   {
        //     std::scoped_lock lock { m };
        //     d.doSomething();
        //   }  // m is automatically unlocked
        // ```
        
        struct MyMutex
        {
          void lock();
          void unlock();
        };
        

        The following non-compliant example uses a comment to record code history.

        // Bug 42 - this call used to be:
        //   calculate ( z , y + 1 );
        calculate ( x , y - 1 );
        
        enum E
        {
        #if 0    // Non-compliant
          E_0    // - this is considered to be commented out code
        #else
          E_1
        #endif
        };
        

        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

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use