Would it be possible to also return something from the module, if it returns something? For example: -- xyz.lua ------ local val = "hello" return val -- main.lua ----- local val = love.filesystem.require "xyz.lua" -- val is now nil, should be "hello" The standard 'requi...

Kaze, you're right... too many years of bad habits...

Sometimes I do catch myself and use the idom "a, b = b, a" but in many other cases the code just looks right to me...

I think the "standard" way to shuffle an array is this: function shuffle(tab) local len = #tab local r, tmp for i = 1, len do r = math.random(i, len) tmp = tab[i] tab[i] = tab[r] tab[r] = tmp end end http://en.wikipedia.org/wiki/Fisher-Yates_shuffle edit: you can also read a bit more at ht...

Just a tiny suggestion (to Kudomiku): Your code is something like if (x) then return x else x = ... return x end That can be written as if not x then x = ... end return x Then you don't repeat the same line twice. Also, I don't think you need those semi-colons (or the brackets around the condition).

As long as you don't have "holes" (i.e. x[1], x[2], x[3] and x[5] are defined, but x[4] is nil), the length operator should do just fine. My suggestion is not to have holes (in fact, my suggestion would be not to mix numbers and strings in the same table: the table's name should give you a...

At the time I was looking for an issue tracker for my work (a couple of years ago). I installed Trac and I can't really say anything bad about it - the form you have to fill is minimal, and the integration between the wiki, the issues and subversion is legendary (you can link from the wiki to subver...

Calm down... where is the LÖVE?! ;) I know what subversion is, I'm not complaining about the release cycle of LÖVE (quite impressed actually, especially with the amount of new features in each release). In fact, all I have is praise for this project. I just don't want it to become ClanLib, that's al...

I have a suggestion that might sound ridiculous, but believe me - it is not. As this is a "Community Ideas" thread, here's an idea to keeps the "community" together: keep releasing and re-releasing the library, even if you haven't made too many changes (in fact, even if it's stab...

This is only my opinion (as usual), but I prefer a single mechanism. It's easier on my brain. My preferred solution is to have LÖVE's default main-loop function dofile "game.conf", then create the window (using the parameters from the config file), then run load() etc. That way, the behavi...

Regarding saving the Lua state, I've found these posts (quite old): http://lua-users.org/lists/lua-l/2000-07/msg00134.html http://lua-users.org/lists/lua-l/2003-11/msg00003.html Don't know if they are still relevant. In any case I wouldn't recommend saving the entire VM even if it's possible - that'...