LÖVE

foo0

It's a long shot, but maybe try to require love.filesystem first.

foo0

At the moment LOVE is using LuaJIT 2.0.3 which corresponds to Lua 5.1. 'bit32' is Lua 5.2 specific I guess. You can use 'bit' instead, which is LuaJIT specific. How to check Lua version example: function luaInfo() local info = "Lua version: " .. _VERSION .. "\n" info = info .. &q...

foo0

In such a case, which is common, just add "stop" before the error message: "stop attempt to index local 'image' (a nil value)" Now you know what to do. Apply this schema to every error message you will get. Most programmers do that trick, it's faster than posting every error mess...

foo0

Code: Select all

if stuff == not false then
	print("blood boiling")
end

foo0

Anyway, I think that mixed solution is rather ugly. It doesn't overwrite conflicting number keys, but overwrites the rest of types? type(k) == "number" doesn't even mean that the key is an array index (e.g. 0, -1, 0.5 are not "valid" indexes that ipairs would respect). It would b...

foo0

You can use table.insert like in your first version:

Code: Select all

function mergetables(...)
	local ret = {}
	for i, tbl in ipairs {...} do
		for k, v in pairs(tbl) do
			if type(k) == "number" then
				table.insert(ret, v)
			else
				ret[k] = v
			end
		end
	end
	return ret
end

foo0

Merge t1 and t2 into t1:

Code: Select all

function table.merge(t1, t2)
	for k, v in pairs(t2) do
		t1[k] = v
	end
	return t1
end

foo0

Store game objects in a separate table, and make grid fields refer to that table. Iterate and update only game objects table. For rendering, compute corners of the visible part of the grid, and render only that area, e.g.: local x0, y0, x1, y1 = computeVisibleArea() for y = y0, y1 do for x = x0, x1 ...

foo0

LuaJIT Extensions : The generated bytecode is portable and can be loaded on any architecture that LuaJIT supports, independent of word size or endianess. However the bytecode compatibility versions must match. Bytecode stays compatible for dot releases (x.y.0 → x.y.1), but may change with major or ...

foo0

Disabling console and adding io.stdout:setvbuf("no") to e.g. conf.lua (as shown here) does the trick. No console, but since Sublime receives output in real time, console would be redundant anyway in that case.

Search found 35 matches

Re: Require in a thread fails

Re: Lua version

Re: How to refer to a table inside another table?

Re: How to refer to a table inside another table?

Re: Small extra functions

Re: Small extra functions

Re: Small extra functions

Re: Would a constantly updating 1024x grid lag?

Re: protection, sharing and keeping your code?

Re: Console output in Sublime