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: 5 rules found
clumsy
    Impact
      Clean code attribute
        1. Loop variables should be declared in the minimal possible scope

           Code Smell
        2. Empty "case" clauses that fall through to the "default" should be omitted

           Code Smell
        3. Redundant casts should not be used

           Code Smell
        4. A "while" loop should be used instead of a "for" loop

           Code Smell
        5. Mergeable "if" statements should be combined

           Code Smell

        Loop variables should be declared in the minimal possible scope

        adaptability - modular
        maintainability
        Code Smell
        Quick FixIDE quick fixes available with SonarLint
        • cppcoreguidelines
        • clumsy

        Why is this an issue?

        More Info

        When a loop variable is not used outside of a loop, it should be declared inside the loop declaration:

        • It improves readability. The scope of the variable is clearly defined.
        • It reduces the number of mistakes. The variable can’t be accidentally misused outside of the loop.
        • Resources are not retained longer than necessary.

        Noncompliant code example

        void f() {
          int i = 0; // Noncompliant: i is not used outside of the loop
          for (i = 0; i < 10; ++i) {
            std::cout << i << std::endl;
          }
        }
        

        Compliant solution

        void f() {
          for (int i = 0; i < 10; ++i) {
            std::cout << i << std::endl;
          }
        }
        
          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