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

should a conformant parser reject symbols containing more than one slash? #22

Closed
bpsm opened this issue Sep 10, 2012 · 2 comments
Closed

Comments

@bpsm
Copy link

bpsm commented Sep 10, 2012

If not, then which slash marks the division between prefix and base name?

@richard-lyman
Copy link

From the sentence fragment, "...once only in the middle of a symbol," I would take a/b/c to be invalid edn since one of two things should have happened to allow that to be valid. Either, remove the extra slash and separate the a from b/c with whitespace, or, remove the extra slash and separate the a/b from c with whitespace.

I don't think there is any ambiguity in the current casual spec about how many / characters may appear in a valid Symbol.

@bpsm
Copy link
Author

bpsm commented Sep 11, 2012

Yea, you're right. My parser rejects symbols with more than one slash, but somehow, I forgot about that sentence in the spec.

@bpsm bpsm closed this as completed Sep 11, 2012
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

2 participants