Open
Conversation
Generated bootstrap.leg.go is different from compiled leg.peg.go, but latter is identical when using itself to compile leg.peg
won't work when rule has dynamic variables
- Add stack operations: RuleActionPush, RuleActionPop
|
+1 |
Defining YYSTYPE as a new type would cause some function calling issues
Contributor
|
Would be nice to see this rebased. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Implemented almost every Leg grammar except for
exp ~ { action }and optional;.Currently has problem with
-switchoptimization, please refer to this issue. Besides that, it works just fine (tested with classic calculator example) .Since there are still some work to do, such as polishing README, I'm posting this pull request just to notify those who are interested in a Leg implementation in Go.
Any advice or fix is welcome. :)
This change is