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
  • ShellShell
  • 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 420
  • Vulnerability14
  • Bug111
  • Security Hotspot19
  • Code Smell276

  • Quick Fix 27
Filtered: 18 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. Non-standard attributes should not be used

           Code Smell
        7. Bit fields should be declared with appropriate types

           Code Smell
        8. Multicharacter literals should not be used

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

           Bug
        10. "#include_next" should not be used

           Code Smell
        11. GNU extensions should not be used

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

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

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

           Code Smell
        15. The "#pragma" directive and the "_Pragma" operator should not be used

           Code Smell
        16. The "#" and "##" preprocessor operators should not be used

           Code Smell
        17. A macro parameter immediately following a "#" operator shall not be immediately followed by a "##" operator

           Code Smell
        18. The "'" or """ or "\" characters and the "/*" or "//" character sequences shall not occur in a "header file" name

           Bug

        The "#" and "##" preprocessor operators should not be used

        intentionality - clear
        maintainability
        Code Smell
        • lock-in
        • misra-c++2023
        • misra-advisory

        Why is this an issue?

        More Info

        This rule is part of MISRA C++:2023.

        Usage of this content is governed by Sonar’s terms and conditions. Redistribution is prohibited.

        Rule 19.3.1 - The # and ## preprocessor operators should not be used

        [cpp.stringize] Unspecified 2
        [cpp.concat] Unspecified 3

        Category: Advisory

        Analysis: Decidable,Single Translation Unit

        Rationale

        The order of evaluation associated with multiple #, multiple ## or a mix of # and ## preprocessor operators is unspecified. It is therefore not always possible to predict the result of macro expansion.

        The use of the ## operator can result in code that is hard to understand.

        Note: M23_393: MISRA C++ 2023 Rule 4.1.3 covers the undefined behaviour that arises if either:

        • The result of a # operator is not a valid string literal; or
        • The result of a ## operator is not a valid preprocessing token.

        Copyright The MISRA Consortium Limited © 2023

          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

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use