-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Escape issue for characeters #2885
Comments
It looks duplicate to #2281, it's a bug.
No it should be |
KvanTTT
added a commit
to KvanTTT/antlr4
that referenced
this issue
Nov 13, 2021
… (display \r\n instead of empty line) fixes antlr#2281, antlr#2885
KvanTTT
added a commit
to KvanTTT/antlr4
that referenced
this issue
Dec 23, 2021
… (display \r\n instead of empty line) fixes antlr#2281, antlr#2885 Restored missed test PredFromAltTestedInLoopBack_1
KvanTTT
added a commit
to KvanTTT/antlr4
that referenced
this issue
Dec 24, 2021
… (display \r\n instead of empty line) fixes antlr#2281, antlr#2885 Restored missed test PredFromAltTestedInLoopBack_1
KvanTTT
added a commit
to KvanTTT/antlr4
that referenced
this issue
Dec 27, 2021
… (display \r\n instead of empty line) fixes antlr#2281, antlr#2885 Restored missed test PredFromAltTestedInLoopBack_1
Merged
@parrt also close |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My parser contains the following characters:
When I target C# the code is good and compiles fine, no errors in C# or Antlr.
But when I compile it against Java, I get:
When I look in the generated Java file I see:
The issue is that
"'\u0022'"
is not valid Java, this should be '\u0022'.Now this can be mitigated by changing the grammer to:
But is this the recommended approach or a bug?
The text was updated successfully, but these errors were encountered: