btw he just fixed this

Okay, to avoid confusion, I changed the infinite loop to a block that repeats 1000 times. That ought to crash it, but it is in no way enough to cause Lua to run out of memory. On my system. it runs fine on official Lua interpreter, but crashes with LuaJIT on the 23rd iteration. or if there's a bug ...

Still, the problems remains of having self everywhere since I'm using locals extensively. Maybe this is just a side affect of Lua making variables globals by default. no, it's because lua doesn't actually have methods. the purpose : serves is to make a function definition or regular table index + f...

not to mention... i don't know how exactly you expect to benefit from it

C

if i see a variable and can't find its declaration in the same file, i ain't gonna be happy

sandbox/dsl function environments are an exception of course (the other being the standard lib, obviously)

There's no global variables, just things required with `require` or passed by parameter. this i avoid globals completely (unless i need to override a built-in for some reason). putting all of your "global" state into modules and requiring them on-demand (into locals!) makes it much easier...

yes

just move the definition of bar() above that of foo.foo(). this will turn foo.foo() into a closure with bar() as an upvalue, which allows it to be used by foo.foo() even though it is no longer in scope by the time you call it

I'd just like to make the piercing jab that bad use of the goto statement has been the underlying cause of two recently discovered dramatic security flaws. not really, the apple bug was mainly the result of not using braces around the if statements, possibly due to a merge/copy+paste error i would ...

Switching booleans without an if-else-statement. function SwitchBoolean( Boolean ) return not Boolean and true or false end I'll try to explain it, but if you have any questions about what this does, see this very well written article . So, `Boolean` would be the boolean ( `true`, `false`, `nil` ) ...