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
Fixing issue from PR #128. Str. match in abstract rule. #134
Conversation
Good work! It is great that textx is such a "defined" project. The unittests and the clarity of the code allows efficient analysis of observed effects and easy fixes! I have a question about rules of the style "A: B| '(' C D ')'. Should such a "partly specialization" be disallowed and yield a grammar error? What should this meta model describe? A is a base of (C and D) together.... (???). See example (I pasted it at the end of the new regression test): I could imagine that if we throw a grammar error if more than one rule is combined in such a case is maybe a good idea? Do you have an idea about the impact (someone uses something like this already?)?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would appreciate to clarify the use of rules like in the example (A:B| C D).
Good point. I think that |
2896d72
to
ffc2937
Compare
This PR has been cleaned up. I did a force push so please update your local branch. Furthermore, referencing multiple rules from a single choice of abstract rule is now explicitly disallowed by raising |
Great! |
Ready to merge... |
Fixes issue discovered in PR #128.
While I was there two bare
except
were fixed also.