You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the scanner, all tokens get position information. In the parser however you can only get line information from a single token, namely the first one. This makes it impossible to report position for error related to other tokens.
As a trival example, consider a rule like FUNCTION code END. The END can be just as wrong as FUNCTION, and it doesn't need to be on the same line, especially if code is not short.
In the current implementation, I would have to change value of every token in the scanner to include position information, which is silly.
The text was updated successfully, but these errors were encountered:
In the scanner, all tokens get position information. In the parser however you can only get line information from a single token, namely the first one. This makes it impossible to report position for error related to other tokens.
As a trival example, consider a rule like
FUNCTION code END
. TheEND
can be just as wrong asFUNCTION
, and it doesn't need to be on the same line, especially ifcode
is not short.In the current implementation, I would have to change
value
of every token in the scanner to include position information, which is silly.The text was updated successfully, but these errors were encountered: