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

define-unparser not provided externally #3

Open
schuster opened this issue Mar 4, 2016 · 3 comments
Open

define-unparser not provided externally #3

schuster opened this issue Mar 4, 2016 · 3 comments

Comments

@schuster
Copy link

schuster commented Mar 4, 2016

Judging from a quick look through the code, it looks like define-parser and define-unparser are the primary ways to parse and unparse languages. The main file provides define-parser, but not define-unparser. Any particular reason why not both?

@schuster
Copy link
Author

schuster commented Mar 4, 2016

Oh, hmm, apparently define-language still defines the unparser named after its defined language, but not the parser. That asymmetry is confusing.

@LeifAndersen
Copy link
Member

I agree. @akeep Do you think it would make sense to make it consistent?

@akeep
Copy link
Member

akeep commented Mar 11, 2016

Yes, absolutely.  In fact, I thought it already was, though it appears the not in the Racket version.

-andy:)

On March 10, 2016 at 4:51:34 PM, Leif Andersen ([email protected]) wrote:

I agree. @akeep Do you think it would make sense to make it consistent?


Reply to this email directly or view it on GitHub.

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

3 participants