If you are parsing a tree node stream, you will encounter som imaginary nodes w/o line/col info. We now search backwards looking for most recent token with line/col info, but notify getErrorHeader() that info is approximate.
The 0-based index into the line where the error occurred.
What is index of token/char were we looking at when the error occurred?
What input stream did the error occur in?
Track the line (1-based) at which the error occurred in case this is generated from a lexer. We need to track this since the unexpected char doesn't carry the line info.
If this is a tree parser exception, node is set to the node with the problem.
The current Token when an error occurred. Since not all streams can retrieve the ith Token, we have to track the Token object. For parsers. Even when it's a tree parser, token might be set.
Return the token type or char of the unexpected input element
Generated using TypeDoc
An extra token while parsing a TokenStream