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: 9 rules found
convention
    Impact
      Clean code attribute
        1. Multiple variables should not be declared on the same line

           Code Smell
        2. Sub and function names should comply with a naming convention

           Code Smell
        3. Comments should not be located at the end of lines of code

           Code Smell
        4. Statements should be on separate lines

           Code Smell
        5. Constant names should comply with a naming convention

           Code Smell
        6. Lines should not end with trailing whitespaces

           Code Smell
        7. Source code should be indented consistently

           Code Smell
        8. Tabulation characters should not be used

           Code Smell
        9. Lines should not be too long

           Code Smell

        Comments should not be located at the end of lines of code

        consistency - formatted
        maintainability
        Code Smell
        • convention

        Why is this an issue?

        This rule verifies that single-line comments are not located at the ends of lines of code. The main idea behind this rule is that in order to be really readable, trailing comments would have to be properly written and formatted (correct alignment, no interference with the visual structure of the code, not too long to be visible) but most often, automatic code formatters would not handle this correctly: the code would end up less readable. Comments are far better placed on the previous empty line of code, where they will always be visible and properly formatted.

        Noncompliant code example

        With the default value for the legalTrailingCommentPattern parameter: ^'\s*[^\s]+$

        a = b + c   ' This is a trailing comment that could be very very long  -- Noncompliant
        d = a + 9 REM This is another trailing comment which could be very very long  -- Noncompliant
        e = a * b ' FIXME  -- allowed
        

        Compliant solution

        ' This very long comment is better placed before the line of code
        a = b + c
        REM This is very long comment which is better placed before the line of code
        d = a + 9
        e = a * b ' FIXME
        
          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