"basic" getters/setters seem kind of pointless imo, at least in a language where you can intercept field access. usually if i want something like this and i'm not being lazy, i'd rather implement attributes/properties/whatever they're called this week... ok so they're still getters/setters...

A better way would be to compile to lua bytecode. There is no good decompiler out there. Actually there are a few working decompilers out there. I've personally used one very successfully. Bytecode generated by regular Lua will not be compatible with different Lua versions (e.g. LuaJIT) or differen...

Remember, kids, premature optimization is bad. In this case, either Inny's or Jasoco's version is fine. Table lookups are unlikely to be a bottleneck, especially in simple games like the above would be a part of. Ignorance is bliss? This is not premature optimization, it's good lua coding habits. Y...

space marines

I'm starting to think the problem is that I've misunderstood the value returned by collectgarbage("count"). Now I think my game is only using a few hundred kilobytes not a few hundred megabytes. According to Lua 5.1 Reference "LUA_GCCOUNT: returns the current amount of memory (in Kby...

i'd make sure your graphics drivers are updated, just to rule that out.

other than that, there's nothing immediately obvious as to what would cause that much slowdown. i'd watch your variable usage in the land.lua file; you have a ton of globals that probably should go into the land table instead

Another option is to put the arguments in a table and use unpack, like so: function foo(...) local args = {...} return function() print(unpack(args)) end end bar = foo('baz') bar() --> 'baz' However, this is problematic when two or more of the arguments are nil. The anonymous function really is the...

the i = block_type line in block_add() is suspect since it's just going to store a reference to one of those block_type tables. so all of your blocks of a specific type are going to be referencing the same data, one of which is the color. you'll probably want to store the alpha per-instance instead

plus, ipairs and a numeric loop using # behave differently: ipairs will stop at the first nil, # will stop at whichever nil it wants (the typical problem it has with holes)

The (massive) speed boost provided by LuaJIT would allow making much more demanding games in LÖVE. the potential massive speed boost code that contains love api calls (or any calls to c libraries not bound through the ffi) likely isn't going to get much faster very mathy or otherwise pure lua code ...