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: 5 rules found
since-c++14
    Impact
      Clean code attribute
        1. Transparent function objects should be used with associative "std::string" containers

           Code Smell
        2. Heterogeneous sorted containers should only be used with types that support heterogeneous comparison

           Bug
        3. The "_t" and "_v" version of type traits should be used instead of "::type" and "::value"

           Code Smell
        4. Standard groupings should be used with digit separators

           Code Smell
        5. Digit separators should be used

           Code Smell

        Standard groupings should be used with digit separators

        intentionality - clear
        maintainability
        Code Smell
        Quick FixIDE quick fixes available with SonarQube for IDE
        • since-c++14
        • pitfall

        Why is this an issue?

        C++14 introduced the ability to use a digit separator (') to split a literal number into groups of digits for better readability.

        To ensure that readability is really improved by using digit separators, this rule verifies:

        • Homogeneity
          • Except for the left-most group, which can be smaller, all groups in a number should contain the same number of digits. Mixing group sizes is at best confusing for maintainers, and at worst a typographical error that is potentially a bug.
        • Standardization
          • It is also confusing to regroup digits using a size that is not standard. This rule enforce the following standards:
            • Decimal numbers should be separated using groups of 3 digits.
            • Hexadecimal numbers should be separated using groups of 2 or 4 digits.
            • Octal and Binary should be separated using groups of 2, 3 or 4 digits.

        Furthermore, using groups with more than 4 consecutive digits is not allowed because they are difficult for maintainers to read.

        Noncompliant code example

        long decimal_int_value     = 1'554'3124;          // Noncompliant; mixing groups of 3 and 4 digits
        double decimal_float_value = 7'91'87'14.3456;     // Noncompliant; using groups of 2 instead of 3 digits
        long hexadecimal_value     = 0x8'3A3'248'6E2;     // Noncompliant; using groups of 3 instead of 2 or 4 digits
        long octal_value           = 0442'03433'13726;    // Noncompliant; using groups of 5 instead of 2, 3 or 4 digits.
        long binary_value          = 0b01010110'11101010; // Noncompliant; using groups of 8 instead of 2, 3 or 4 digits.
        

        Compliant solution

        long decimal_int_value     = 15'543'124;
        double decimal_float_value = 7'918'714.3456;
        long hexadecimal_value     = 0x83'A324'86E2;
        long octal_value           = 04'4203'4331'3726;
        long binary_value          = 0b0101'0110'1110'1010;
        

        Exceptions

        No issue is raised on the fractional or exponent part of floating point numbers, only the integral part should comply.

          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