HIGHLIGHT Product Documentation

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

• If & else statements can be taxing for the CPU
• CompareTo Empty is unreliable as it tests reference equality, not object equality
• EXIT without parameters cause issues in the script
• A static or unqualified import is harmful to readability.
• Background processes are created by KSH
• Conditional comments are designed exclusively for IE
• Avoid Backslash to continue command
• JSP can handle exceptions
• Multiple instructions on the same line decreases code readability.
• Exported Variables are global in scope and store values
• Care must be taken while selecting a Candidate key as Primary
• Untrusted data can be prevented by validation
• EXIT closes the entire script
• Semicolon is used to terminate statement
• GoTo is primitive & outside one's control
• Empty Catches cause code errors & unreliability
• Short code identifiers worsens collaboration
• Javabeans & Tags are useful in JSP as they encapsulate
• Too many pipe commands cause inefficiency
• CASE is better to understand than DECODE
• Pipes are an inefficient way of dealing with commands
• HTML comments do not add to user-friendliness
• Short local variables could lead to bugs and misinformation
• Correct indentation allows for better understanding and bug prevention
• Symmetrical listing allows for better understanding and bug prevention
• Variable declaration creates an instance in the class
• The first line activates the KSH interpreter
• Specify precision otherwise error occurs
• File Naming Convention (FNC) helps in organization
• Deprecated features makes code less resilient