-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Parser breaks on documents with special characters #162
Comments
Weird, as far as UT2004 goes, the string is actually escaped:
|
I had this happen in the following file, that does not seem to contain special characters: DeusExText.zip |
Did a quick check from interest - extension starts to work when you comment |
@Shtoyan or by appending FYI: This is caused by the hacky-code in the ANTLR parser
|
Unfortunately I have to admit I'm unable to fix this issue in a way that ANTLR would understand. A proper solution to this #directive parsing would be to switch the lexer's channel when a statement directive has been detected, but ANTLR is incapable of this as far as I know. |
No way to just ignore all |
Describe the bug
When the parser stumbles on special characters it will fail with the following error:
Appears to be caused by the following code, when an unescaped string literal is proceeded by an eventual hash character:
Screenshots
No response
The text was updated successfully, but these errors were encountered: