HIGHLIGHT Product Documentation

This documentation is for reference only. Original Highlight Product Documentation is available at https://doc.casthighlight.com/

• SELECT clauses with many columns tend to be complex in nature.
• Local variables allows variables to be relegated to a function
• Avoid dangerous types
• eval() evaluates statements
• Comparison operators compare values
• Less efficient datatypes cause interchangeability issues
• Documentation facilitates Code Maintainability
• Not all Tag libraries should be imported
• Empty Catches may cause security risks
• Conditional expressions should not be too complex
• Object Qualification improves readability
• Mixing DDL & DML operations can cause recompilation
• A Return Statement in the middle of a command makes it unreadable
• End keyword highlights end of execution
• Using {curly braces} is less error-prone
• Switch statements should have a default case specified
• Database columns, functions, triggers and procedures should be commented
• Avoid exposing too many attributes
• Avoid using functions before their declaration
• Avoid repetitive access to nested members
• Code should be stripped out of suspicious comments
• Semicolons seem to be missing too frequently
• Structural code complexity may be too high
• The code contains too many lines containing several instructions
• Method parameters should have their description tag
• A line of code shouldn't be too long (to help readability)
• Code indentation, line, and character encoding formats should be consistent
• Attribute, classes and methods should follow a naming convention
• Avoid literal numbers (i.e. Magic numbers are not so magic)
• Too many controversial, unsafe or deprecated keywords in procedure divisions