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
When the lexer sees a non-ASCII illegal token, it emits only the first byte as the cause of the error, resulting in a mangled message.
How to reproduce
Compile the following (non-conforming) source with satysfi (SATySFi version 0.0.6).
あ
Then we get an error with an invalid codepoint. (In the following output, the invalid codepoint is replaced with U+FFFD � replacement character, but the actual output is the first byte of あ.)
$ satysfi -o /dev/null a.saty ---- ---- ---- ---- target file: 'null' dump file: 'a.satysfi-aux' (will be created) parsing 'a.saty' ...! [Syntax Error at Lexer] at "a.saty", line 1, characters 0-1: illegal token '�' in a program area
Related Issues
#312 reports an issue with the error position, but the root cause is the same: Unicode-aware treatment of errors.
The text was updated successfully, but these errors were encountered:
When the lexer sees a non-ASCII illegal token, it emits only the first byte as the cause of the error, resulting in a mangled message.
How to reproduce
Compile the following (non-conforming) source with satysfi (SATySFi version 0.0.6).
Then we get an error with an invalid codepoint. (In the following output, the invalid codepoint is replaced with U+FFFD � replacement character, but the actual output is the first byte of あ.)
Related Issues
#312 reports an issue with the error position, but the root cause is the same: Unicode-aware treatment of errors.
The text was updated successfully, but these errors were encountered: