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 674
  • Vulnerability13
  • Bug139
  • Security Hotspot19
  • Code Smell503

  • Quick Fix 91
Filtered: 10 rules found
obsolete
    Impact
      Clean code attribute
        1. Digraphs should not be used

           Code Smell
        2. Trigraphs should not be used

           Code Smell
        3. GNU extensions should not be used

           Code Smell
        4. The "register" storage class specifier should not be used

           Code Smell
        5. Increment should not be used to set boolean variables to 'true'

           Code Smell
        6. Standard C++ headers should be used

           Code Smell
        7. Obsolete POSIX functions should not be used

           Code Smell
        8. Code annotated as deprecated should not be used

           Code Smell
        9. Deprecated code should be removed

           Code Smell
        10. Deprecated attributes should include explanations

           Code Smell

        Standard C++ headers should be used

        consistency - conventional
        maintainability
        Code Smell
        • obsolete

        Why is this an issue?

        The iostream.h header was provided with the first C++ compiler, CFront, and became the de facto standard. During the formal standardization process of C++, many shortcomings in iostream.h were fixed, but at the cost of introducing incompatibilities. Therefore, it was decided not to change the existing iostream.h and introduce the standard version as a new iostream header.

        Modern compilers tend to remove the support of the legacy iostream.h header, and migrating to the standard version is encouraged.

        This rule applies not only to iostream, but to all standard C++ headers.

        Noncompliant code example

        #include <iostream.h> // Noncompliant
        #include <fstream.h>  // Noncompliant
        

        Compliant solution

        #include <iostream>
        #include <fstream>
        
          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