-
Notifications
You must be signed in to change notification settings - Fork 65
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
Delete of undefined "type" returns weird 115 error #354
Comments
dvander
added a commit
that referenced
this issue
Sep 8, 2019
The two-pass parser treats any unknown variable as a function, and if those leak into expressions, it can lead to weird error messages. Bug: issue #354 Test: manual test
dvander
added a commit
that referenced
this issue
Sep 8, 2019
The two-pass parser treats any unknown variable as a function, and if those leak into expressions, it can lead to weird error messages. Bug: issue #354 Test: manual test
Thanks for the report - the error will print it as a function now. That's about as good as it can get with the current parser (which assumes all unknown names are functions). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tested with SourcePawn Compiler 6431.
Error:
Test Case:
I don't know if this errors should be normal, but looks pretty weird.
The text was updated successfully, but these errors were encountered: