This repository has been archived by the owner on Feb 4, 2019. It is now read-only.
Better parsing of statement lists #322
Merged
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
| @@ -1181,6 +1213,7 @@ public void Pipeline3Test() | |||
|
|
|||
| static dynamic ParseInput(string s) | |||
| { | |||
| PowerShellGrammar.Parser.Context.TracingEnabled = true; | |||
There was a problem hiding this comment.
If this flag is set, the parser will trace what kind of shifts and reductions it performs.
When I tried different ways of writing this grammar, it turned out to be very useful for understanding the problems my grammar had while I debugged my tests.
|
should i have merged this first? there is a conflict now :-( |
|
Nope, both pull requests include changes to the same lines. I'll merge it and update it. |
JayBazuzi
added a commit
that referenced
this pull request
Dec 17, 2014
Better parsing of statement lists
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
These commits fix the issue described in #7.
It was a real pain to modify this grammar correctly, but I finally managed to get a grammar with even less shift/reduce conflicts as before :)