Community
Participate
Working Groups
I am trying to use bind a different lexer than the generated InternalMyDslLexer. The generated MyDslParser class creates InternalMyDslLever. It should be using guice to get the lexer. -- KD
Although it may be possible to inject the lexer, it is no option for the parser. One solution may be to use two template methods for the InternalParser and InternalLexer class. Clients may use their own <Language>Parser subtype and overwrite these template methods.
(In reply to comment #1) > Although it may be possible to inject the lexer, it is no option for the > parser. I did not understand this part. Since bindLexer() is available in the runtime module, I assumed that we should be using guice to create the lexer everywhere. I changed the generated MyDslParser.java as follows and it works. @Inject private Lexer lexer ; and then in the parse() function: lexer.setCharStream(in); instead of: org.xtext.example.parser.antlr.internal.InternalMyDslLexer lexer = new org.xtext.example.parser.antlr.internal.PythonizedMyDslLexer(in); -- KD
That's right. That's why I said: > Although it may be possible to inject the lexer, it is no option for the > parser. It is possible for the lexer but not for the "InternalParser" as it gets some arguments passed into the constructor, that cannot be injected. However, you are right, the template method for the InternalLexer is not necessary.
(In reply to comment #3) I am trying to implement python type indent/dedent as discussed here: http://www.eclipse.org/newsportal/article.php?id=1959&group=eclipse.modeling.tmf#1959 All in all the hack works. But I spent couple of hours to figure out that a guice is not used to create the lexer in MyDslParser.java. I am planning to post it sometime - though I think it is not fit for Xtext proper. It will be nice if you can leave bindLexer() and use guice to create lexer in MyDslParser. I did not post a patch because it is too simple a change. -- KD
Fixed in HEAD
Closing bug which were set to RESOLVED before Eclipse Neon.0.
