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: 10 rules found
brain-overload
    Impact
      Clean code attribute
        1. "GoTo" statements should not be used

           Code Smell
        2. "GoSub" statements should not be used

           Code Smell
        3. Subs and functions should not be too complex

           Code Smell
        4. "Select Case" statements should not have too many "Case" clauses

           Code Smell
        5. Subs and functions should not have too many lines

           Code Smell
        6. "Case" clauses should not have too many lines

           Code Smell
        7. Magic numbers should not be used

           Code Smell
        8. Procedures should not have too many parameters

           Code Smell
        9. Expressions should not be too complex

           Code Smell
        10. Files should not have too many lines of code

           Code Smell

        "GoSub" statements should not be used

        intentionality - clear
        maintainability
        Code Smell
        • brain-overload

        Why is this an issue?

        How can I fix it?

        More Info

        The GoSub statement in VB6 is an unstructured control flow statement. It can lead to complex and difficult-to-maintain code, as well as potential stack overflow errors due to improper return handling.

        Modern programming practices recommend using proper subroutine or function calls instead, which provide better readability, maintainability, and error handling.

          Available In:
        • SonarQube ServerAnalyze code in your
          on-premise CI

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use