Is it a bug of plugin?

[UniquePerch]

For example:
I have a parser defination of [seq]:

Notice the last defination of [seq] : seq_function SEMI?

It has been defined as followd:

I also have a lexer defination of [POINT_D] (defined in another g4 file):

Then I import a whole lexer defination（However,if I use tokenVocab to associated lexer file, it also happens）,use the plugin to generate parse tree(input:"seq(1,2)"), something unexpected happened , plugin regard my input "(1,2)" as a POINT_D lexer.

I don't know whether it is my mistake or it is just a bug of this plugin?

[bjansen]

Hi,

In your current grammar, the input (1,2) can match either one of these:

• POINT_D
• LR_BRACKET seq_expression RR_Bracket

But because the lexing phase happens before the parsing phase, ANTLR will match it to a POINT_D. Then it will complain that it was expecting a seq_expression but got a POINT_D instead.

I think you should rework your grammar to transform your POINT_D lexing rule to a parsing rule.