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: 7 rules found
preprocessor
    Impact
      Clean code attribute
        1. Lines starting with "#" should contain valid preprocessing directives

           Bug
        2. There shall be at most one occurrence of the # or ## operators in a single macro definition

           Code Smell
        3. Macros used in preprocessor directives should be defined before use

           Bug
        4. Function-like macros should not be invoked without all of their arguments

           Bug
        5. Function-like macros should not be used

           Code Smell
        6. Pre-defined macros should not be defined, redefined or undefined

           Code Smell
        7. Macro names should comply with a naming convention

           Code Smell

        Macros used in preprocessor directives should be defined before use

        intentionality - logical
        reliability
        Bug
        • based-on-misra
        • preprocessor

        Why is this an issue?

        More Info

        An attempt to use an undefined identifier may elicit a warning from the preprocessor. Or it may not; the preprocessor may simply assume that the undefined token has a value of 0.

        Therefore macro identifiers should not be used in preprocessor directives until after they have been defined, and this limited usage should be enforced with the use of definition tests.

        Noncompliant code example

        #if x > 0  /* x assumed to be zero if not defined */
        #include SOMETHING_IMPORTANT
        #endif
        
        #ifdef y  /* Okay; y is not evaluated */
        #if y > 0 /* Okay; y must be defined to reach this point */
        ...
        #endif
        #endif
        

        Compliant solution

        #define x 10
        ...
        #if x > 0
        #include SOMETHING_IMPORTANT
        #endif
        
        #if defined ( y ) && ( y > 0 )  /* more compact form, same result as before */
        ...
        #endif
        
          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