Terence Parr
Terence Parr
Yeah, something is hosed with parsing of that grammar itself. Seems like a bug in plugin
Something in the grammar is causing static grammar analysis in plugin to go nuts but NOT from command line.
Wow. it takes ANTLR 6s on my fast box to process your parser .g4 file!!!! I have a trivial main() that exhibits...it's antlr issue not plugin :) Confirmed command line...
@KitsuneAlex I moved issue to antlr, leaving this open... https://github.com/antlr/antlr4/issues/3711
Are all split-out lexers required to have `Lexer` as a suffix or is that just a default? Wondering if we can look at the grammar file name and determine whether...
I think in config dialog code we can force it to share a common set of values. :) Hmm...are we assuming XParser and XLexer is only way to associated split...
Coming to the conclusion that maybe I should just leave things as is until I understand this problem and the source code better. Some tangled relationships in there.
Can you give me the steps to reproduce this?
Sounds good. not easy to get it right ;)
Tom said it was just a toy. I haven't bumped up this in priority yet. Sorry. Sent from my iPhone > On Dec 21, 2015, at 8:06 AM, Ivan Kochurkin...