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

Attribute grammar design #13

Merged
merged 14 commits into from
Feb 3, 2022
Merged

Attribute grammar design #13

merged 14 commits into from
Feb 3, 2022

Conversation

Quincunx271
Copy link
Owner

@Quincunx271 Quincunx271 commented Jan 23, 2022

For #11 , just how to implement an "attribute grammar" isn't quite clear, so this document will explore how to do that.

To do:

  • Clearly define the problem.
  • Research attribute grammars and different implementations (e.g. Boost.Spirit).
  • Dream about the ideal kind of interface.
  • Think about the most minimal kind of interface, with enough flexibility to allow for the potential of the dream.
  • Gather these thoughts in the document.

The topic of having the parser be able to emit an AST rather than a
`bool` is complicated enough that it makes sense to gather thoughts in a
document rather than writing code with no direction.
Markdown is more widely readable. As this is not a specification, it's
nicer to just have a markdown document.
@Quincunx271 Quincunx271 added the documentation Improvements or additions to documentation label Jan 23, 2022
@Quincunx271 Quincunx271 marked this pull request as ready for review February 3, 2022 05:46
@Quincunx271 Quincunx271 merged commit abc438d into main Feb 3, 2022
@Quincunx271 Quincunx271 deleted the attribute-grammar-design branch February 3, 2022 05:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant