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: 24 rules found
convention
    Impact
      Clean code attribute
        1. Literal suffix "L" for long integers shall be upper case

           Code Smell
        2. Source code should only use /* ... */ style comments

           Code Smell
        3. Format strings should comply with ISO standards

           Code Smell
        4. Label names should comply with a naming convention

           Code Smell
        5. Enumeration values should comply with a naming convention

           Code Smell
        6. Enumeration names should comply with a naming convention

           Code Smell
        7. Comment styles "//" and "/* ... */" should not be mixed within a file

           Code Smell
        8. Preprocessor directives should not be indented

           Code Smell
        9. "union" names should comply with a naming convention

           Code Smell
        10. Track "TODO" and "FIXME" comments that do not contain a reference to a person

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

           Code Smell
        12. "struct" names should comply with a naming convention

           Code Smell
        13. File names should comply with a naming convention

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

           Code Smell
        15. Track lack of copyright and license headers

           Code Smell
        16. Comments should not be located at the end of lines of code

           Code Smell
        17. Statements should be on separate lines

           Code Smell
        18. Local variable and function parameter names should comply with a naming convention

           Code Smell
        19. Field names should comply with a naming convention

           Code Smell
        20. Lines should not end with trailing whitespaces

           Code Smell
        21. Files should end with a newline

           Code Smell
        22. Tabulation characters should not be used

           Code Smell
        23. Lines should not be too long

           Code Smell
        24. Function names should comply with a naming convention

           Code Smell

        Statements should be on separate lines

        consistency - formatted
        maintainability
        Code Smell
        • convention

        Why is this an issue?

        Putting multiple statements on a single line lowers the code readability and makes debugging the code more complex.

        foo(); bar(); // Noncompliant
        

        Write one statement per line to improve readability.

        foo();
        bar();
        

        Exceptions

        The rule ignores:

        • control flow statements with a single nested statement
        if (condition) doSomething();     // Compliant by exception
        while (condition) doSomething();  // Compliant by exception
        
        • case or default statements containing a single statement followed by break
        switch (foo) {
          case  0: doSomething(); break;    // Compliant by exception
          default: doSomething(); break;    // Compliant by exception
        }
        
        • statements enclosed in curly braces on the same line
        auto lambda = [](int x) { doSomething(x); return x; }; // Compliant by exception
        
          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