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
 
Tags
    Impact
      Clean code attribute
        1. Pointer and reference parameters should be "const" if the corresponding object is not modified

           Code Smell
        2. Non-standard characters should not occur in header file names in "#include" directives

           Bug
        3. Functions should not be declared at block scope

           Code Smell
        4. Literal suffix "L" for long integers shall be upper case

           Code Smell
        5. Digraphs should not be used

           Code Smell
        6. The first element of an array should not be accessed implicitly

           Code Smell
        7. A single L in a literal suffix should only be used for long values

           Code Smell
        8. Loop variables should be declared in the minimal possible scope

           Code Smell
        9. Pointer and reference local variables should be "const" if the corresponding object is not modified

           Code Smell
        10. "sizeof" should not be called on pointers

           Bug
        11. Control characters should not be used in literals

           Code Smell
        12. Parameters should be passed in the correct order

           Code Smell
        13. Redundant casts should not be used

           Code Smell
        14. Multiple variables should not be declared on the same line

           Code Smell
        15. Unused local variables should be removed

           Code Smell
        16. Octal values should not be used

           Code Smell
        17. A "while" loop should be used instead of a "for" loop

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

           Code Smell
        19. Redundant pairs of parentheses should be removed

           Code Smell

        A single L in a literal suffix should only be used for long values

        intentionality - clear
        maintainability
        Code Smell
        Quick FixIDE quick fixes available with SonarLint
        • since-c++11

        Why is this an issue?

        How can I fix it?

        More Info

        The type of an integer literal depends on three parameters: the value of the literal, whether it is written in decimal or not, and its suffix.

        A literal with a single L (or l) will usually be of a (possibly unsigned) long type. But if its value cannot be represented in this type, it will be of a (possibly unsigned) long long type instead.

        In such a case, it is more straightforward to use LL in the literal suffix, which unambiguously specifies a long long type.

        Note: This rule targets classical integer literals, not user-defined literals whose type is entirely determined by their suffix.

          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
          10.7

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use