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
  • 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 315
  • Vulnerability13
  • Bug76
  • Security Hotspot19
  • Code Smell207

  • Quick Fix 19
Filtered: 15 rules found
misra-c++2008
    Impact
      Clean code attribute
        1. Pointer and reference parameters should be "const" if the corresponding object is not modified

           Code Smell
        2. "abort", "exit", "getenv" and "system" from <stdlib.h> should not be used

           Bug
        3. "offsetof" macro should not be used

           Code Smell
        4. There shall be at most one occurrence of the # or ## operators in a single macro definition

           Code Smell
        5. 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
        6. #include directives in a file should only be preceded by other preprocessor directives or comments

           Code Smell
        7. Functions should not be defined with a variable number of arguments

           Code Smell
        8. Evaluation of the operand to the sizeof operator shall not contain side effects

           Bug
        9. Switch statement conditions should not have essentially boolean type

           Code Smell
        10. Switch labels should not be nested inside non-switch blocks

           Code Smell
        11. A cast shall not remove any const or volatile qualification from the type of a pointer or reference

           Code Smell
        12. If a function has internal linkage then all re-declarations shall include the static storage class specifer

           Code Smell
        13. Functions should not be declared at block scope

           Code Smell
        14. Assembly language should be encapsulated and isolated

           Code Smell
        15. Control should not be transferred into a complex logic block using a "goto" or a "switch" statement

           Code Smell

        Functions should not be declared at block scope

        intentionality - clear
        maintainability
        Code Smell
        Quick FixIDE quick fixes available with SonarLint
        • misra-c++2008
        • misra-c2004

        Why is this an issue?

        How can I fix it?

        More Info

        It is rarely useful to declare a function at block scope. Such a function will not get special access to any name in its enclosing scope, and therefore, it is equivalent but clearer to declare it instead in the enclosing namespace.

        Additionally, when a function is declared at block scope, the intent is often not to declare a function but instead to declare and initialize a variable. This problem is nicknamed the most vexing parse and stems from the fact that some syntaxes can be ambiguous, and that in that case the language unintuitively favors function declaration:

        void f() {
          int a;
          string b();
          short c(short (a));
        }
        
        • b could be interpreted as:
          • A variable of type string with empty initialization or
          • A function with no argument and returning a string.
          The second interpretation is selected.
        • Similarly, c could be interpreted as:
          • A variable of type short initialized with the value a converted to short or
          • A function that takes a parameter named a (with extra parentheses) of type short and returning a short
          Here again, the second interpretation is selected.

        There are several ways to write the code differently so that b and c can only be interpreted as variables. For instance:

        void f() {
          int a;
          string b {};
          auto c = short (a);
        }
        

        By raising issues on local function declaration, this rule helps detect when a function is inadvertently declared.

          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