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.

Sign up for GitHub

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

Jump to bottom

Parser failure when EOF exists where semicolon is expected at end of statement #5

Open
csnover opened this issue Oct 21, 2011 · 0 comments
Open

Parser failure when EOF exists where semicolon is expected at end of statement #5

csnover opened this issue Oct 21, 2011 · 0 comments

Comments

@csnover
Copy link

csnover commented Oct 21, 2011

EOF should be considered a valid statement terminator, but currently it generates an error. For example, given the following code:

foo()

the following error is generated: [2, 5]unexpected token (tEof:'EOF'); expected ;
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@csnover