To summarize: Utilities throw UtilEvalError. ASTs throw EvalError. ASTs catch UtilEvalError and rethrow it as EvalError using toEvalError( Node ).
Philosophically, EvalError and UtilEvalError corrospond to RuntimeException. However they are constrained in this way in order to add the context for error reporting.
UtilTargetError
| Access | Constructor and Description |
|---|---|
| protected | |
| public |
| Modifier and Type | Method and Description |
|---|---|
| public EvalError | toEvalError(String
may be null for no additional message. msg, SimpleNode node, CallStack callstack)Re-throw as an eval error, prefixing msg to the message and specifying the node. |
| public EvalError |
| UtilEvalError | back to summary |
|---|---|
| protected UtilEvalError() | |
| UtilEvalError | back to summary |
|---|---|
| public UtilEvalError(String s) | |
| toEvalError | back to summary |
|---|---|
| public EvalError toEvalError(String msg, SimpleNode node, CallStack callstack) Re-throw as an eval error, prefixing msg to the message and specifying the node. If a node already exists the addNode is ignored. | |
| toEvalError | back to summary |
|---|---|
| public EvalError toEvalError(SimpleNode node, CallStack callstack) | |