Re: Static metaprogramming with Lua 5.2.

Subject: Re: Static metaprogramming with Lua 5.2.
From: Fabien &lt;fleutot+lua@ ... &gt;
Date: Fri, 11 Apr 2014 12:06:17 +0200

@Steve it sure would be nice to do some porting. However:

if I wait a bit more I can go straight to Lua 5.3 ;
it's not clear whether the highest priority target would be Lua 5.{2,3} or LuaJIT.

Somewhere on my radar, there's LuaJIT-lang-toolkit [https://github.com/franko/luajit-lang-toolkit]. It converts ASTs into LuaJIT bytecode, but unfortunately defines its own AST format. It would be really nice to convert it to the Metalua format, or at least hack an AST transcoder. I'd even help anyone willing to take the lead on such a project... :-)

On Fri, Apr 11, 2014 at 11:42 AM, steve donovan <steve.j.donovan@gmail.com> wrote:

On Fri, Apr 11, 2014 at 11:28 AM, Dominique Torette <Dominique.Torette@spacebel.be> wrote:

But from the documentation, it seems that Metalua (only?) support Lua 5.1 (https://github.com/fab13n/metalua/tree/master).
Should I expect problem to run Metalua generated byte code on a Lua 5.2 VM?

You would have a problem - 5.1 bytecode is not compatible with 5.2.

Your best bet is any tool that transforms original source into valid Lua source, and then compile that. Unless some clever person has a 5.2 -> 5.1 bytecode transformer[1]....or you can persuade Fabien that it's important to do the ML port.

[1] would be mostly mechanical - that word 'mostly' is the problem ;)