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: 29 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. The value returned by a function shall be "used"

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

           Code Smell

        "extern" shouldn't be used on member definitions

        intentionality - clear
        reliability
        Bug
        • unused

        Why is this an issue?

        More Info

        Data members and member functions cannot be defined as external, although entire objects can. When a member is declared as extern, the compiler simply ignores the keyword, making it both extraneous and confusing.

        Noncompliant code example

        class C {
          void fun();
        };
        
        extern void C::fun() { // Noncompliant
        }
        

        Compliant solution

        class C {
          void fun();
        };
        
        void C::fun() {
        }
        
          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
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use