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: 17 rules found
misra-advisory
    Impact
      Clean code attribute
        1. The "goto" statement should not be used

           Code Smell
        2. "std::vector" should not be specialized with "bool"

           Code Smell
        3. Variables of array type should not be declared

           Code Smell
        4. "Unscoped enumerations" should not be declared

           Code Smell
        5. Functions with "limited visibility" should be "used" at least once

           Code Smell
        6. All variables should be initialized

           Code Smell
        7. Variables should be captured explicitly in a non-"transient lambda"

           Code Smell
        8. The "#" and "##" preprocessor operators should not be used

           Code Smell
        9. A "noexcept" function should not attempt to propagate an exception to the calling function

           Bug
        10. Classes should not be inherited virtually

           Code Smell
        11. A "declaration" should not declare more than one variable or member variable

           Code Smell
        12. There should be no unnamed namespaces in "header files"

           Code Smell
        13. A cast should not convert a pointer type to an integral type

           Code Smell
        14. The "declaration" of an object should contain no more than two levels of pointer indirection

           Code Smell
        15. The names of the "standard signed integer types" and "standard unsigned integer types" should not be used

           Code Smell
        16. "#include" directives should only be preceded by preprocessor directives or comments

           Code Smell
        17. Variables with "limited visibility" should be "used" at least once

           Code Smell

        Variables should be captured explicitly in a non-"transient lambda"

        intentionality - complete
        maintainability
        Code Smell
        • pitfall
        • since-c++11
        • misra-c++2023
        • misra-advisory

        Why is this an issue?

        More Info

        This rule is part of MISRA C++:2023.

        MISRA Rule 8.1.2

        Category: Advisory

        Analysis Type: Decidable,Single Translation Unit

        Amplification

        This rule applies to capture by value and capture by reference.

        Rationale

        Naming the variables captured by a lambda expression clarifies its dependencies. This allows variables captured by reference and pointers captured by value to be more easily identified, helping to ensure that they are not dangling when the lambda is called.

        This issue cannot occur for a transient lambda [1], so there is no need to explicitly capture its variables.

        Example

        void bar( double val, double min, double max )
        {
          auto const easedVal = [&]()
          {
            if ( val < min ) { return ( val + min ) / 2; }
            if ( val > max ) { return ( val + max ) / 2; }
            return val;
          }();                                          // Compliant - called immediately
        
          auto const ease = [&]()
          {
            if ( val < min ) { return ( val + min ) / 2; }
            if ( val > max ) { return ( val + max ) / 2; }
            return val;
          };                                            // Non-compliant
          ease();                                       //   - not an immediate call
        }
        
        template< typename It, typename Func >
        bool f1( It b, It e, Func f )                   // f1 does not store f
        {
          for ( It it = b; it != e; ++it )
          {
            if ( f( *it ) )                             // f is called
            {
              return true;
            }
          }
        
          return false;
        }
        
        template< typename Cont, typename Func >
        bool f2( Cont const & c, Func f )               // f2 does not store f
        {
          return f1( std::begin(c), std::end(c), f );   // f passed to non-storing function
        }
        
        void foo( std::vector< size_t > const & v, size_t i )
        {
          bool b1 = f1( v.cbegin(), v.cend(),
                        [&]( size_t elem ) { return elem == i; } );  // Compliant
          bool b2 = f2( v,
                        [&]( size_t elem ) { return elem == i; } );  // Compliant
        }
        
        struct Speedometer
        {
          std::vector< std::function< void ( double ) > > observers;
        
          template< typename Func >
          void addObserver( Func f )                    // addObserver stores f
          {
            observers.push_back( f );                   // Copying f to the std::function
          }
        };
        
        void process( std::function< Speedometer() > );
        
        auto f3()
        {
          Speedometer s;
        
          process( [&](){ return s; } );                // Non-compliant - conversion to
                                                        //  std::function stores the lambda
          return [=]() { return s; };                   // Non-compliant - implicit capture
        }
        
        
        void addLoggers( Speedometer s, std::ostream & os )
        {
          s.addObserver( [&]( double speed )            // Non-compliant - implicit capture
                         { os << speed; });
          s.addObserver( [&os]( double speed )          // Compliant - explicit capture
                         { os << speed; } );
          s.addObserver( []( double speed )             // Compliant - no capture
                         { std::cout << speed; } );
        }
        

        Glossary

        [1] Transient lambda

        A lambda is transient when:

        • It is immediately invoked; or
        • It is passed to a function that does not store it.

        A function does not store a lambda when:

        • The function is defined in the same translation unit as the lambda; and
        • The lambda is only copied or moved when it is passed as an argument; and
        • The function only calls the lambda and/or passes the lambda to another function that does not store it.

        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

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use