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
VB6

VB6 static code analysis

Unique rules to find Bugs, Security Hotspots, and Code Smells in your VB6 code

  • All rules 45
  • Bug1
  • Security Hotspot1
  • Code Smell43
Filtered: 7 rules found
performance
    Impact
      Clean code attribute
        1. Variable data types should be declared explicitly

           Code Smell
        2. The bang ("!") operator should not be used

           Code Smell
        3. "Asc[W]" should not be called on string constants

           Code Smell
        4. "Chr[W]$()" should not be used for certain characters

           Code Smell
        5. String-specific functions should be used

           Code Smell
        6. Strings should not be set to empty string

           Code Smell
        7. Strings should not be compared with empty string

           Code Smell

        "Chr[W]$()" should not be used for certain characters

        intentionality - efficient
        maintainability
        Code Smell
        • performance

        Why is this an issue?

        It is more efficient to skip the function invocation and use the predefined string constants rather than calling Chr$() or ChrW$() for the following numbers:

        • 0 - vbNullChar
        • 8 - vbBack
        • 9 - vbTab
        • 10 - vbLf
        • 11 - vbVerticalTab
        • 12 - vbFormFeed
        • 13 - vbCr
        • 13+10 - vbCrLf | vbNewLine
        • 34 - ""

        Noncompliant code example

        Dim myChar As Char
        myChar = Chr$(0)
        

        Compliant solution

        Dim myChar As Char
        myChar = vbNullChar
        
          Available In:
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Enterprise
          Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use