[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: RE: Lua for Windows needs help
- From: Benoit Germain <bgermain@...>
- Date: Wed, 2 Mar 2011 15:25:10 +0100
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com]
> On Behalf Of steve donovan
> Sent: Wednesday, March 02, 2011 3:03 PM
> To: Lua mailing list
> Subject: Re: Lua for Windows needs help
> On Wed, Mar 2, 2011 at 3:52 PM, RJP Computing <firstname.lastname@example.org>
> > * Should Lua and LuaJIT v2.x be included?
> It's a bit of a bugger to mix two different kinds of Lua on Windows,
> since extensions bind to a particularly named DLL. I think LuaJIT is
> mature enough to be the main engine...
The problem is that LuaJIT2 doesn't support the full Lua C API. To be specific, lua_dump() is not implemented. As an example, because of this, it is not possible to transfer a Lua function from one state to another, which breaks the Lanes module almost completely. Also, any binary module that embeds Lua code in precompiled bytecode format won't run with LuaJIT since the VM implementations and compilers are totally different.
> That's the cool/interesting angle - pick a core set of modules which
> work fine across the board. I know that you have been pushing for
> wxLua and it certainly is the most mature cross-platform kit we have
> at the moment. IUP should also be there as well.
IUP won't run with LuaJIT2 for the above reason.