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
Triggered by `example/C.cf`.
ANTLR/Java does not deal well with a parser name `cParser` because with Java 20 `cParserListerner` becomes an unbound symbol.
The lower case `c` is due to the package name sanitization introduced in:
- #212
So this problem exists since 2.8.4, but many only surfaced with recent Java versions that are more strict with case.
A solution is to use a capitial CamelCase for the prefix of `Parser` and `Lexer`, but keep the snake_case for the package name.
Triggered by `example/C.cf`.
ANTLR/Java does not deal well with a parser name `cParser` because with Java 20 `cParserListerner` becomes an unbound symbol.
The lower case `c` is due to the package name sanitization introduced in:
- #212
So this problem exists since 2.8.4, but many only surfaced with recent Java versions that are more strict with case.
A solution is to use a capitial CamelCase for the prefix of `Parser` and `Lexer`, but keep the snake_case for the package name.
If my input is
my-grammar.cf
, bnfc will create java code with package namemy-grammar
which is not legal.The text was updated successfully, but these errors were encountered: