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

#comment: parse error / unmatched delimiter #12

Closed
jkleiser opened this issue Feb 27, 2019 · 1 comment
Closed

#comment: parse error / unmatched delimiter #12

jkleiser opened this issue Feb 27, 2019 · 1 comment

Comments

@jkleiser
Copy link

If a .janet script file ends with a #comment and that comment does not have a linefeed character at the end, then the script may run as planned, but at the end this message comes:

parse error in XYZ.janet around byte NNN: unmatched delimiter
@bakpakin
Copy link
Member

bakpakin commented Feb 27, 2019

Thanks for the issue. For language bugs, please put them in the Janet repo instead.

This was a parser issue, fixed in janet, commit 3014a59c3e7f3c8d0c3707852173841eaf78c759

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