HIGHLIGHT Product Documentation

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

• Highlight integrates into your ecosystem using our public API
• Release Notes - Highlight March 2018
• Avoid classes using incorrect dynamic allocation
• Manage transactions when changing tables
• Avoid classes with missing destructor declarations in header files
• Avoid macros defining constants
• Lack of multiple-inclusion protection in header files
• Too many unconditional branches may end to Spaghetti Code
• Crossing the Parameter limit can cause bugs
• RETURN should be used to terminate a database query or a stored procedure
• Run Highlight code scans into your CI/CD environments
• Using {curly braces} is less error-prone
• Release Notes - Highlight October 2017
• Avoid using risky patterns too frequently
• Declaring errors prevents security risks
• Illegal exception occurs when user declares a standard exception.
• Incomplete JSP fragments can cause readability errors.
• CDATA is an XML construct which can only be read by JSP
• Aliases can complicate and hide commands that hamper resiliency
• Commenting on setProperty() method allows for software to be resilient
• Group Use declarations help cut verbosity in the code
• JSP standard is XML-compliant but certain elements cannot be mixed causing agility issues
• Javascript in HTML can be unreadable and cause reliability issues
• Multiple packages in the same file have multiple references can cause agility issues
• CASE cannot be an instruction without a WHEN clause
• Double semicolon is required for a bash syntax to correctly parse the command
• Native Dynamic SQL is easier to use than DBMS SQL.
• $$ creates unique temporary filenames
• Artifacts and Subqueries decrease code agility
• Multiple lines makes code harder to read