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

Trying to call a null function in Lua gives a bad error message #128

Open
nwinter opened this issue Dec 14, 2014 · 0 comments
Open

Trying to call a null function in Lua gives a bad error message #128

nwinter opened this issue Dec 14, 2014 · 0 comments
Labels

Comments

@nwinter
Copy link
Contributor

nwinter commented Dec 14, 2014

After @basicer's recent change to save the Lua parser from generating code from bad player code that crashes escodegen, at least it doesn't hang, but we give a bad error message for trying to call a nil function like this:

a = function() end
a():b()

or

a = {}
a:b:c()

result in error messages where it tells you the name of the nil thing is __luaTemp$1234.

@nwinter nwinter added the bug label Dec 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant