Consistent naming for combined and separated grammars about antlr4 HOT 1 OPEN

This is particularly annoying if your project starts out with a combined grammar and you later need to convert it to separate lexer/parser grammars. Obviously you can't fix the default behavior without an incompatible change to the generated names, but you could add an option or options to enable some other behavior.

Note that if you name the parser grammar Foo then you get the mostly the same names as in the combined grammar with the exception of the parser class, which is just called Foo instead of FooParser. You can then create a subclass named FooParser to get pretty close to the combined grammar behavior.

Given that the primary problems are going to come about from going from a combined grammar to a split grammar and not the other way around, I think that providing an option to let you specify the name of the parser class might be sufficient.

from antlr4.