Skip to content
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

discrepancy between actual SPGenearator and declaration string in simpleparsegrammar.py #14

Open
hernot opened this issue Jun 27, 2022 · 0 comments

Comments

@hernot
Copy link

hernot commented Jun 27, 2022

Just a quick question as i came across while trying to figure a solution for issue #13.

Are there any reasons why the SPGenerator defines

unreportedname := '<', ts, name, ts, '>'
reportedname     := '>', ts, name, ts, '<'

while all the examples in documentation, the ebnf grammar in the documentation and the declaration string define the same as

unreportedname := '<', name, '>'
expandedname   := '>', name, '<'

Is this discrepancy between documented and actual definition by intention?
Which definition should be used to resolve and which should be adopted accordingly?

For testing i temporarily pick documented definition and adopt actual.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant