Rules

#Dim declaring an initial valueMinorCode Smell
  • Reliability
    • Instruction
 maintainability
#Dim directive with no associated typeMajorCode Smell
  • Maintainability
    • Readability
 coding-guidelines, maintainability
$CASE(...) with no default caseMajorCode Smell
  • Reliability
    • Instruction
 clarity, coding-guidelines
Avoid using short names for ObjectScript functionsInfoCode Smell
  • Maintainability
    • Readability
 coding-guidelines, confusing
Avoid using short names for system functionsInfoCode Smell
  • Maintainability
    • Readability
 coding-guidelines, confusing
Boolean expression not surrounded by parenthesesMinorCode Smell
  • Reliability
    • Logic
 clarity, coding-guidelines
ByRef method argument not assignedMajorCode Smell
  • Reliability
    • Data
 probable-bug
Call to a method that belongs to a csp class is discouragedInfoCode Smell
  • Reusability
    • Reusability Compliance
    • Modularity
  • Maintainability
    • Understandability
 coding-guidelines, design
Catch not inspecting the thrown exceptionMajorCode Smell
  • Reliability
    • Exception handling
 coding-guidelines
Class declared as "Not ProcedureBlock"BlockerVulnerability
  • Security
    • Security compliance
 design
Class has too many methodsMajorCode Smell
  • Changeability
    • Logic
 design, maintainability
Class has too many parametersMajorCode Smell
  • Changeability
    • Logic
 design
Class has too many propertiesMajorCode Smell
  • Changeability
    • Logic
 design
Class not declared abstractInfoCode Smell
  • Changeability
    • Data
 coding-guidelines, convention
Class not foundCriticalBug
  • Reliability
    • Resource
 runtime-failure
Confusing use of numeric test operatorsInfoCode Smell
  • Maintainability
    • Readability
 confusing, deprecation
Depth of Inheritance Tree too large for classMajorCode Smell
  • Reusability
    • Reusability Compliance
 design
Empty catch blockMajorCode Smell
  • Changeability
    • Logic
 design
Empty methodCriticalCode Smell
  • Reliability
    • Logic
 clarity, suspicious
Idenfitiers differing only by caseCriticalCode Smell
  • Maintainability
    • Readability
 clumsy, confusing
Implicit access to last globalCriticalCode Smell
  • Reliability
    • Instruction
 clarity, coding-guidelines, confusing
Implicit inspection of $TESTCriticalCode Smell
  • Maintainability
    • Understandability
 clarity, confusing
Incompatible argument type in a methodMinorBug
  • Reliability
    • Instruction
 runtime-failure
LCOM4 too high for classMajorCode Smell
  • Reusability
    • Modularity
 design
Legacy flow control with more than one statementMajorCode Smell
  • Maintainability
    • Readability
 coding-guidelines, confusing
Legacy flow control with no associated statementsBlockerCode Smell
  • Reliability
    • Logic
 deprecation, probable-bug, trap
Line label name is the same as a builtin commandCriticalCode Smell
  • Reliability
    • Instruction
 probable-bug, trap
Local variable name is invalidCriticalBug
  • Reliability
    • Instruction
 reliability, trap
Local variable name is too longCriticalBug
  • Reliability
    • Data
 trap
Local variable not previously declaredMinorCode Smell
  • Maintainability
    • Readability
 clarity, coding-guidelines
Method argument not passed by referenceMajorCode Smell
  • Reliability
    • Data
 probable-bug
Method argument with no typeMajorCode Smell
  • Maintainability
    • Understandability
 coding-guidelines, maintainability
Method arguments with default values not at the endMajorCode Smell
  • Maintainability
    • Readability
 coding-guidelines, confusing
Method declared as "ProcedureBlock = 0"BlockerVulnerability
  • Security
    • Security compliance
 design, maintainability
Method has too many argumentsMajorCode Smell
  • Efficiency
    • Efficiency compliance
 design, maintainability, performance
Method has too many linesCriticalCode Smell
  • Maintainability
    • Maintainability compliance
 design, maintainability
Method has too many statementsCriticalCode Smell
  • Maintainability
    • Maintainability compliance
 design, maintainability
Method is too complexCriticalCode Smell
  • Maintainability
    • Maintainability compliance
 design, maintainability
Method is too deeply nestedCriticalCode Smell
  • Changeability
    • Logic
 design, maintainability
Method lack return typeMajorCode Smell
  • Reliability
    • Instruction
 coding-guidelines, probable-bug
Method never invokedMajorCode Smell
  • Reliability
    • Instruction
 design, maintainability
Method not foundCriticalBug
  • Reliability
    • Instruction
 runtime-failure
Method uses too many variablesMajorCode Smell
  • Efficiency
    • Efficiency compliance
 design, maintainability, performance
Method with unexpected argumentsCriticalBug
  • Reliability
    • Instruction
 runtime-failure
Methods failing to return a result on all code pathsBlockerBug
  • Reliability
    • Fault tolerance
 bug
Missing argument(s) in method callBlockerBug
  • Reliability
    • Data
 runtime-failure
Missing parentheses in the Boolean expressionMinorCode Smell
  • Reliability
    • Logic
 clarity, coding-guidelines
No quit (or return) foundCriticalBug
  • Reliability
    • Data
 runtime-failure
Non-checked SQLCODE after &SQLMajorCode Smell
  • Reliability
    • Data
 probable-bug, reliability
Object property must be MultiDimensional on $GET and $DATABlockerBug
  • Security
    • Errors
 bug, runtime-failure
OPEN without a timeoutBlockerCode Smell
  • Reliability
    • Fault tolerance
 probable-bug, trap
Output method argument not assignedMajorCode Smell
  • Reliability
    • Data
 probable-bug
Package %ZEN is deprecatedInfoCode Smell
  • Reliability
    • Reliability compliance
 deprecation
Package naming conventionMinorCode Smell
  • Maintainability
    • Maintainability compliance
    • Readability
 clarity, coding-guidelines
Property name declared with quotesInfoCode Smell
  • Maintainability
    • Readability
 clarity, coding-guidelines
Property not foundCriticalBug
  • Reliability
    • Data
 runtime-failure
Property of type %String without a MAXLENMajorCode Smell
  • Efficiency
    • Efficiency compliance
 performance
Quit whitout argumentsCriticalBug
  • Reliability
    • Data
 runtime-failure
Reassignment to a method argument passed by valueMajorCode Smell
  • Reliability
    • Data
 coding-guidelines, probable-bug
Return value of method not declaredCriticalCode Smell
  • Reliability
    • Instruction
 probable-bug
Several statements on a single lineMajorCode Smell
  • Maintainability
    • Readability
 clarity, coding-guidelines, confusing
SQL Delimited Identifiers with double quotesBlockerBug
  • Reliability
    • Instruction
 bug, runtime-failure
Subscript access to a non MultiDimensional propertyBlockerBug
  • Security
    • Errors
 runtime-failure
Test result of %SaveMajorCode Smell
  • Reliability
    • Exception handling
 bug, runtime-failure
Try block is too longMajorCode Smell
  • Changeability
    • Logic
 design, maintainability
Undocumented class/methodMajorCode Smell
  • Maintainability
    • Understandability
 maintainability
Unnecessary ELSEMinorCode Smell
  • Maintainability
    • Understandability
 coding-guidelines
Unsafe namespace changeCriticalCode Smell
  • Reliability
    • Instruction
 probable-bug
Unused method argumentMajorCode Smell
  • Efficiency
    • Efficiency compliance
 maintainability, performance
Usage of GOTOBlockerCode Smell
  • Changeability
    • Logic
 confusing, deprecation, maintainability
Usage of legacy block styleMajorCode Smell
  • Maintainability
    • Readability
 clarity, coding-guidelines, deprecation
Usage of legacy for flow control statementsCriticalCode Smell
  • Changeability
    • Logic
 coding-guidelines, deprecation
Usage of legacy if/else flow control statementsCriticalCode Smell
  • Changeability
    • Logic
 coding-guidelines, deprecation
Usage of non short circuit boolean operatorsCriticalCode Smell
  • Reliability
    • Logic
 performance, reliability
Usage of QUIT to exit a methodMajorCode Smell
  • Maintainability
    • Understandability
 cache-2014, clarity, coding-guidelines
Use of "Set $ECODE"BlockerCode Smell
  • Reliability
    • Exception handling
 confusing, deprecation, design, maintainability
Use of $ETRAPBlockerCode Smell
  • Reliability
    • Exception handling
 confusing, deprecation
Use of $PROPERTY, $PARAMETER, $METHOD or $CLASSMETHODCriticalCode Smell
  • Security
    • API abuse
 design, maintainability
Use of $ZERROR is discouragedInfoCode Smell
  • Reliability
    • Exception handling
 deprecation, design
Use of $ZF(-1) is deprecatedMajorCode Smell
  • Reliability
    • Exception handling
 deprecation, design
Use of $ZF(-2) is deprecatedMajorCode Smell
  • Reliability
    • Exception handling
 deprecation, design
Use of $ZORDER is deprecatedInfoCode Smell
  • Security
    • API abuse
 deprecation
Use of $ZTRAP is discouragedInfoCode Smell
  • Reliability
    • Exception handling
 deprecation, design
Use of $ZUTIL may be replacedInfoCode Smell
  • Security
    • API abuse
 deprecation
Use of &sqlMajorCode Smell
  • Efficiency
    • Efficiency compliance
 performance
Use of a macro as a statementMajorCode Smell
  • Maintainability
    • Understandability
 coding-guidelines, confusing, maintainability
Use of BREAKBlockerCode Smell
  • Reliability
    • Instruction
 probable-bug, trap
Use of custom getters or settersBlockerCode Smell
  • Reliability
    • Instruction
 design, maintainability, reliability
Use of OPEN is discouragedCriticalCode Smell
  • Security
    • API abuse
 confusing, deprecation
Use of postconditionalsMinorCode Smell
  • Maintainability
    • Readability
 clarity, coding-guidelines
Use of the HANG commandBlockerCode Smell
  • Reliability
    • Instruction
 probable-bug
Use of XECUTECriticalVulnerability
  • Reliability
    • Instruction
 coding-guidelines, deprecation, performance
Uses of 'FIXME' tagsInfoCode Smell
  • Reliability
    • Reliability compliance
 maintainability, reliability, suspicious
Uses of 'TODO' tagsInfoCode Smell
  • Reliability
    • Reliability compliance
 maintainability, reliability, suspicious
Using =' instead of '= for null oref checksBlockerCode Smell
  • Reliability
    • Instruction
 probable-bug, trap
Variable declared but not usedMajorCode Smell
  • Efficiency
    • Efficiency compliance
 maintainability, performance
Variable name is the same as a builtin commandCriticalCode Smell
  • Security
    • API abuse
 confusing
Variable name with non ASCII letters/digitsCriticalCode Smell
  • Portability
    • Portability Compliance
 coding-guidelines, portability
Variable not foundCriticalBug
  • Reliability
    • Data
 runtime-failure
Width of Inheritance Tree too large for classMajorCode Smell
  • Reusability
    • Reusability Compliance
 design
cachéQuality
cachéQuality
© 2024 Lite Solutions