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

Add table of equivalent forms to Rule Reference #223

Closed

Conversation

eyepatchParrot
Copy link

When starting with the S expression example, I wanted a quick reference guide to quickly get up to speed in terms of already familiar languages like PEG and regex, and in terms of rules I was already familiar with: if_must from must.

Every row in every table which maps between pegtl rules depends only on rows above it, and every rule in the s expression example is covered. The long lines provide space alignment between columns in markdown, but with the links gets excessive.

This is just describing what I had in mind, let me know what you think or if it's not suitable for the project / goes somewhere else.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 92.432% when pulling be2881c on eyepatchParrot:equivalence_tables into be89131 on taocpp:master.

@d-frey
Copy link
Member

d-frey commented Oct 28, 2020

Thank you for the idea, I think it might be useful, although I'll discuss with Colin (when time permits) which table should go where. Personally, I think the reference section should not be containing PEG -> PEGTL or regex -> PEGTL tables, they might be better suited for other parts of the documentation.

@d-frey d-frey closed this in f1bbe47 Nov 19, 2020
@ColinH
Copy link
Member

ColinH commented Nov 19, 2020

For now we've kept the combinator table, albeit on the "getting started" page, but have removed the other tables since they would need to be greatly extended in order to be really useful, which then creates its own set of issues.

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

Successfully merging this pull request may close these issues.

4 participants