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: 25 rules found
bad-practice
    Impact
      Clean code attribute
        1. Pointer and reference parameters should be "const" if the corresponding object is not modified

           Code Smell
        2. Reserved identifiers should not be defined or declared

           Code Smell
        3. Only standard forms of the "defined" directive should be used

           Code Smell
        4. Function-like macros should not be used

           Code Smell
        5. Recursion should not be used

           Code Smell
        6. "continue" should not be used

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

           Bug
        8. Functions should be declared explicitly

           Code Smell
        9. Names of well-known C standard library macros and functions should not be used as identifiers

           Code Smell
        10. Macros should not be used as replacements for "typedef" and "using"

           Code Smell
        11. Size of bit fields should not exceed the size of their types

           Code Smell
        12. Pointer and reference local variables should be "const" if the corresponding object is not modified

           Code Smell
        13. Argument of "printf" should be a format string

           Code Smell
        14. Loops with at most one iteration should be refactored

           Bug
        15. "if" statements should be preferred over "switch" when simpler

           Code Smell
        16. Track uses of "NOSONAR" comments

           Code Smell
        17. Deprecated attributes should include explanations

           Code Smell
        18. The literal value zero shall be the only value assigned to "errno"

           Code Smell
        19. The operands of "bitwise operators" and "shift operators" shall be appropriate

           Bug
        20. "Dynamic memory" should not be used

           Code Smell
        21. Precautions shall be taken in order to prevent the contents of a "header file" being included more than once

           Code Smell
        22. All "#else", "#elif" and "#endif" preprocessor directives shall reside in the same file as the "#if", "#ifdef" or "#ifndef" directive to which they are related

           Code Smell
        23. Functions shall not call themselves, either directly or indirectly

           Code Smell
        24. The target type of a pointer or "lvalue" reference parameter should be const-qualified appropriately

           Code Smell
        25. "Trigraph-like sequences" should not be used

           Code Smell

        The target type of a pointer or "lvalue" reference parameter should be const-qualified appropriately

        consistency - conventional
        maintainability
        Code Smell
        • bad-practice
        • 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.1.1 - The target type of a pointer or lvalue reference parameter should be const-qualified appropriately

        Category: Advisory

        Analysis: Decidable,Single Translation Unit

        Amplification

        The target type of a named pointer or reference parameter should be const-qualified, unless:

        • It is not an object type; or
        • The parameter is assigned to a pointer or reference with a non-const target type; or
        • The target object is modified within the function.

        For the purposes of this rule, an object is also considered to be modified if it is passed as a pointer to non-const parameter or a non-const reference parameter, including use as the implicit this parameter of a non-const member function.

        This rule does not apply to parameters:

        • That are unnamed; or
        • Of virtual functions; or
        • Of function templates; or
        • Of functions or lambdas declared within the scope of a template.

        Note: this rule also applies to pointer parameters declared using array syntax.

        Rationale

        Consistent application of this guideline results in function signatures that more accurately reflect the behaviour of the functions within the project, making it less likely that a developer will falsely assume that a call will not result in the modification to an object.

        The rule does not apply to virtual functions as different overrides of the function may or may not modify the target object, and all overrides will need to omit const-qualification if one or more of the overrides requires that the target type be non-const. Similarly, for templates, only some instantiations may modify the target object.

        Exception

        This rule does not apply to main whose signature, which does not use const-qualification, is defined within the C++ Standard.

        Example

        void f1(       int8_t *       p1,     // Compliant - *p1 modified
                 const int8_t *       p2,     // Compliant - *p2 not modified, but is const
                       int8_t *       p3,     // Non-compliant - *p3 not modified, no const
                       int8_t * const p4,     // Non-compliant - *p4 not modified, no const
                       int8_t         a[3] )  // Non-compliant - 'a' decays to int8_t *
        {
           *p1 = *p2 + *p3 + *p4 + a[ 2 ];
        }
        
        auto & f2( int32_t &  i,              // Compliant
                   int32_t && j,              // Rule does not apply - rvalue reference
                   int32_t &    )             // Rule does not apply - unnamed parameter
        {
          return i;                           // Assigning to non-const reference
        }
        
        auto f3( std::vector< int32_t > & x )  // Compliant - even though x.begin has an
        {                                      //             equivalent const overload
          return x.begin();                    // Non-const member function
        }
        
        auto f4( std::vector< int32_t > & x )  // Non-compliant
        {
          return x.cbegin();                   // Const member function
        }
        
        template< typename T >
        struct A
        {
          void foo ( T       & t,              // Rule does not apply - in template scope
                     int32_t & i )             // Rule does not apply - in template scope
          {
            t.f( i );                          // t and/or i may or may not be modified,
          }                                    // depending on the signature of T::f
        };
        

        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