lua-users home
lua-l archive

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


On Sun, Jul 17, 2011 at 11:21 PM, James McKaskill <james@foobar.co.nz> wrote:
> The bad:
> - 64bit support is broken. It was actually broken before, but you
> would only hit it if your allocator returned pointers > 4GB.

isn't LuaJIT similarly limited? i think all Lua objects are
constrained to 1GB...


> The callbacks are done by jitting an appropriate stub whose lifetime
> is tied to the lua function. Also its currently hard coded to use the
> lua_State that was present when the lua function was converted to a
> function pointer.

if i understand it correctly, this sounds reasonable; since a
different lua_State isn't guaranteed to contain the same Lua function.
IOW: a specific Lua function implicitly specifies a specific
lua_State, right?


> Also vararg callbacks aren't supported and never will be as there
> isn't enough information to figure out how to push the arguments into
> lua.

right now, i can't remember any C API with vararg callbacks.



-- 
Javier