-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nested Rules (#34) #107
Nested Rules (#34) #107
Conversation
note to self: I think in the refactoring process I lost the lines that let |
4f35262
to
38b5949
Compare
also make Rule_Context a stack rather than a parameter
I've changed the syntax, so the example above is
|
FIND definitely could share unifications and regexes with its subrules, but I don't feel like wading into the semantics of that atm. |
Any attachment to |
Segfault where Input:
Grammar:
|
the segfault, as with so many other errors I had to fix, was overly-aggressive search-and-replace at the beginning of the process. |
This PR adds
WITH
rules, which are followed by a list of rules in{}
, where the latter rules are only run if theWITH
matches. These rules will be run with the same values of_TARGET_
and_MARK_
asFIND
.closes #18
closes #34
relevant to #45 and #103