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: 13 rules found
lock-in
    Impact
      Clean code attribute
        1. "<time.h>" should not be used

           Code Smell
        2. "<stdio.h>" should not be used in production code

           Code Smell
        3. "<signal.h>" should not be used

           Bug
        4. Preprocessor operators "#" and "##" should not be used

           Code Smell
        5. Bitwise operators should not be applied to signed operands

           Bug
        6. Bit fields should be declared with appropriate types

           Code Smell
        7. Multicharacter literals should not be used

           Code Smell
        8. Arguments evaluation order should not be relied on

           Bug
        9. "#include_next" should not be used

           Code Smell
        10. GNU extensions should not be used

           Code Smell
        11. The "sizeof" and "alignof" operator should not be used with operands of a "void" type

           Bug
        12. Keywords introduced in later specifications should not be used as identifiers

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

           Code Smell

        Keywords introduced in later specifications should not be used as identifiers

        consistency - conventional
        maintainability
        Code Smell
        • lock-in

        Why is this an issue?

        While keywords introduced in later standards can legally be used as identifiers in code compiled to earlier standards, doing so will eventually cause problems. Such code will cause compile errors if (when) the compiler is upgraded, and fixing those errors could be difficult and painful.

        Additionally, such misuse of keywords has the potential to thoroughly confuse people who are unfamiliar with the code base, possibly leading them to introduce additional errors.

        For these reasons, the earlier this practice is stopped, the better.

        This rule flags instances of the following keywords used as identifiers:

        C99

        inline, restrict, _Bool, _Complex, _Noreturn, _Static_assert, _Thread_local

        C11

        _Alignas, _Alignof, _Atomic, _Generic, _Imaginary

        C++11

        alignas, alignof, char16_t, char32_t, constexpr, decltype, noexcept, nullptr, static_assert, thread_local

        C++20

        concept, requires, constinit, consteval, co_await, co_return, co_yield, char8_t

        Noncompliant code example

        int inline = 0;
        

        Compliant solution

        int inline_count = 0;
        
          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