|
Thanks Fabien, I agree that the 5.3 is just around the corner and I should upgrade my VM to 5.3, but not to a LuaJIT (I’m on a microcontroller). What should be the effort to port Metalua to 5.3? Is it an easy task that could be overtaken by someone else? Could I help? Static metaprogramming is a really cool/useful feature, I would be a pity if it will not further maintained.
Dominique T. From: lua-l-bounces@lists.lua.org [mailto:lua-l-bounces@lists.lua.org]
On Behalf Of Fabien @Steve it sure would be nice to do some porting. However:
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 ;)
-- ------------------------------------------------------------------------------ E-MAIL DISCLAIMER The present message may contain confidential and/or legally privileged information. If you are not the intended addressee and in case of a transmission error, please notify the sender immediately and destroy this E-mail. Disclosure, reproduction or distribution of this document and its possible attachments is strictly forbidden. SPACEBEL denies all liability for incomplete, improper, inaccurate, intercepted, (partly) destroyed, lost and/or belated transmission of the current information given that unencrypted electronic transmission cannot currently be guaranteed to be secure or error free. Upon request or in conformity with formal, contractual agreements, an originally signed hard copy will be sent to you to confirm the information contained in this E-mail. SPACEBEL denies all liability where E-mail is used for private use. SPACEBEL cannot be held responsible for possible viruses that might corrupt this message and/or your computer system. ------------------------------------------------------------------------------- |