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 798
  • Vulnerability14
  • Bug173
  • Security Hotspot19
  • Code Smell592

  • Quick Fix 99
Filtered: 27 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. MSVC-specific extensions should not be used

           Code Smell
        8. Code should not rely on features beyond the configured C++ standard

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

           Code Smell
        10. Multicharacter literals should not be used

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

           Bug
        12. "auto" should not be used as a storage class specifier

           Code Smell
        13. "#include_next" should not be used

           Code Smell
        14. GNU extensions should not be used

           Code Smell
        15. Reference types should not be qualified with "const" or "volatile"

           Code Smell
        16. Partial specialization syntax should not be used for function templates

           Code Smell
        17. String literals should not be immediately followed by macros

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

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

           Code Smell
        20. "<cstdio>" should not be used

           Code Smell
        21. "<ctime>" should not be used

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

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

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

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

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

           Bug
        27. A program shall conform to ISO/IEC 14882:2017 (C++17)

           Code Smell

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

        intentionality - logical
        reliability
        Bug
        Quick FixIDE quick fixes available with SonarQube for IDE
        • lock-in
        • misra-c++2023
        • misra-required

        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.2.3 - The ' or " or \ characters and the /* or // character sequences shall not occur in a header file [1] name

        [lex.header] Implementation 2

        Category: Required

        Analysis: Decidable,Single Translation Unit

        Rationale

        Use of the following are conditionally-supported with implementation-defined behaviour:

        • The ' or " or \ characters, and the /* or // character sequences are used between < and > delimiters in a header file [1] name preprocessing token;
        • The ' or \ characters, or the /* or // character sequences are used between the " delimiters in a header file [1] name preprocessing token.

        Note: even on systems where \ is the path separator, most implementations will accept the / character as an alternative.

        Example

        #include "file.h"       // Compliant
        #include "fi'le.h"      // Non-compliant
        #include "path\file"    // Non-compliant
        #include "path\\file"   // Non-compliant
        #include "path/file"    // Compliant
        

        Glossary

        [1] Header file

        A header file is considered to be any file that is included during preprocessing (for example via the #include directive), regardless of its name or suffix.

        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