Error conditions and messages
In case the script is malformed or provides invalid data to functions or operators, an exception may occur. It is then handled by the software calling the interpreter and the exception class name is logged. Below there is a list of the error conditions that can occur.
In case of ASTER script execution issue, the script execution breaks and the Int4 tooling produces an error messages which should be helpful to address the problem at hand. The error message contains the exception name, textual description and sometimes additional information, as in the example below.
Examples

Example of error message when RETURN is used outside a function definition.

Example of error message when wrong number of parameters was provided to a function call.
Generic error classes
Exception Class Name | Explanation in Natural Language |
---|---|
| A general error class for ASTER-related issues. |
| Execution resulted in an unexpected error. |
Specialized error classes
Exception Class Name | Explanation in Natural Language |
---|---|
| Function was called with invalid parameters. |
| Function was called with an incorrect number of parameters. |
| Requested function was not found. |
| Attempted a mathematical operation that cannot be performed (e.g., division by zero). |
| Index was out of the valid range, typically for arrays. |
| Invalid escape sequence was encountered in the code. |
| Function object was invalid or malformed. |
| Invalid lvalue (left-hand side of an expression) was encountered. |
| Regular expression provided as parameter could not be interpreted and was considered invalid. |
| Key was not found in a data structure like a map or dictionary. |
| Logical errors encountered during the execution, such as inconsistent conditions or invalid usage of control flow operators. |
| An operator was used in an unary context but it is not unary. The only unary operators are |
| An unknown or unsupported operator was encountered. |
| Parser encountered code that could not be interpreted, most likely due to an invalid syntax. |
| Stack shadowing failed - error likely related to variable scoping. |
| Parser found unmatched parentheses or brackets in the code. |