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

        Local variable and function parameter names should comply with a naming convention

        consistency - identifiable
        maintainability
        Code Smell
        • convention

        Local variables and function parameters should be named consistently to communicate intent and improve maintainability. Rename your local variable or function parameter to follow your project’s naming convention to address this issue.

        Why is this an issue?

        How can I fix it?

        More Info

        A naming convention in software development is a set of guidelines for naming code elements like variables, functions, and classes.
        Local variables and function parameters hold the meaning of the written code. Their names should be meaningful and follow a consistent and easily recognizable pattern.
        Adhering to a consistent naming convention helps to make the code more readable and understandable, which makes it easier to maintain and debug. It also ensures consistency in the code, especially when multiple developers are working on the same project.

        This rule checks that local variable and function parameter names match a provided regular expression.

        What is the potential impact?

        Inconsistent naming of local variables and function parameters can lead to several issues in your code:

        • Reduced Readability: Inconsistent local variable and function parameter names make the code harder to read and understand; consequently, it is more difficult to identify the purpose of each variable, spot errors, or comprehend the logic.
        • Difficulty in Identifying Variables: The local variables and function parameters that don’t adhere to a standard naming convention are challenging to identify; thus, the coding process slows down, especially when dealing with a large codebase.
        • Increased Risk of Errors: Inconsistent or unclear local variable and function parameter names lead to misunderstandings about what the variable represents. This ambiguity leads to incorrect assumptions and, consequently, bugs in the code.
        • Collaboration Difficulties: In a team setting, inconsistent naming conventions lead to confusion and miscommunication among team members.
        • Difficulty in Code Maintenance: Inconsistent naming leads to an inconsistent codebase. The code is difficult to understand, and making changes feels like refactoring constantly, as you face different naming methods. Ultimately, it makes the codebase harder to maintain.

        In summary, not adhering to a naming convention for local variables and function parameters can lead to confusion, errors, and inefficiencies, making the code harder to read, understand, and maintain.

        Exceptions

        This rule ignores const variables.

          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