lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

My general opinion is that, if you are suffering from these kinds of errors, you are "developing too fast."

Which is to say, if you took time to ensure there were no typos, added asserts, metatable index guards where appropriate, etc. then the problems would basically just go away. Yes it would take some effort. And the amount of effort and appropriateness of these measures depends on the program and the programmer. E.g. whether you tend to make a lot of typos, or how much syntax highlighting support your editor gives you.

So in general, my advice is to ensure you are taking time and measures to deal with these issues, if you are having them. Just that's more of a development workflow issue than a language environment issue.

On Tue, Mar 19, 2013 at 4:23 PM, William Sumner <> wrote:
Lua's behavior of silently returning nil for undefined variables can lead to bugs that propagate undetected. Has thought been given to changing this in a major version update, or are there reasons for retaining this behavior? I'm aware of strict.lua, but it only provides safety for global/module scope.