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: 28 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
        25. User-defined identifiers shall have an appropriate form

           Code Smell
        26. The "#include" directive shall be followed by either a "<filename>" or ""filename"" sequence

           Bug
        27. A "declaration" should not declare more than one variable or member variable

           Code Smell
        28. The lowercase form of "L" shall not be used as the first character in a literal suffix

           Code Smell

        A "declaration" should not declare more than one variable or member variable

        consistency - formatted
        maintainability
        Code Smell
        Quick FixIDE quick fixes available with SonarQube for IDE
        • convention
        • 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 10.0.1 - A declaration [1] should not declare more than one variable or member variable

        Category: Advisory

        Analysis: Decidable,Single Translation Unit

        Amplification

        An init-declarator-list or a member-declarator-list should consist of a single init-declarator or member-declarator respectively.

        Structured bindings are permitted by this rule.

        Rationale

        Where multiple declarators appear in the same declaration [1], the type of an identifier may not meet developer expectations.

        Example

        int32_t   i1; int32_t j1;                 // Compliant
        int32_t   i2, * j2;                       // Non-compliant
        int32_t * i3,
                & j3 = i2;                        // Non-compliant
        
        struct point
        {
          int32_t x, y;                           // Non-compliant
        };
        
        std::map< char, char > map = f();
        
        auto [ loc, inserted ] =
          map.insert( make_pair( 'A', 'a' ) );    // Compliant - structured binding
        

        Glossary

        [1] Declaration

        A declaration introduces the name of an entity into a translation unit (see [basic.def]/1).

        An entity may be declared several times. The first declaration of an entity in a translation unit is called an introduction [2]. All subsequent declarations are called redeclarations [3].

        A definition [4] is a declaration, as described in [basic.def]/2.

        [2] Introduction

        See declaration [1].

        [3] Redeclaration

        See declaration [1].

        [4] Definition

        See declaration [1].

        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