Expose mode_stack on Lexer
#24
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rrevenantt
force-pushed
the
master
branch
3 times, most recently
from
0e0c2b1 to
3c36c28
Compare
rrevenantt
force-pushed
the
master
branch
3 times, most recently
from
c402ec4 to
43bb370
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm attempting to use a grammar originally generated to Java, which contains a number of lexer actions that behave differently depending on the current mode / contents of the mode stack. This patch simply exposes the
mode_stackfield, just as it would be exposed to subclasses in a generated Java lexer.