It's been so long since I worked on it, I hardly remember what was left. I think module/language/lua/notes.org covers most of it.
The main tasks would be: - Standard library compliance (the existing modules are missing some functions, and there is no debug/coroutine module) - module function - Multiple values and variable arguments. Lua expressions can return multiple values. Lua assignments can involve multiple values in confusing ways. (This is very easy for the Lua runtime to handle, but as I recall bolting it onto tree-il was frustrating me quite a bit). - Fix the REPL. Scheme is all about expressions, Lua is all about statements. Somehow, despite writing a Lua implementation, I never realized that you evaluate Lua expressions in the REPL by typing "return true" or "= true" for short. Typing a normal expression, such as "true", is an error. And I don't know whether you can convince the Guile REPL to play nice with that worldview. - I was personally planning to pretty much rewrite parser.scm and compile-tree-il.scm as I wasn't happy with the length or complexity of them. I would think the parser could be rewritten using a parser generator, and the code generator could be simplified quite a bit (look at ecmascript). - Performance improvements. Never did get around to benchmarking it. - Import the Lua language test suite and ensure compliance http://www.lua.org/tests - Consider implementing Lua 5.2. They added a bitwise manipulation library and simplified the module system quite a bit. On Tue, May 21, 2013 at 3:42 PM, Phil <theseaisinh...@gmail.com> wrote: > Hey guys, > > I was just thinking about Guile Lua (and feeling guilty that I never > did finish it). Anyway, I never did make any progress after my 2012 > posts. I got a little discouraged while implementing Lua's multiple > values everywhere, to be honest. > > By all means, feel free to take over the lua branch. As long as it's > okay with Ludo, Andy, whoever is in charge these days, I think you > should push to it with reckless abandon instead of submitting patches > since it isn't used in guile (yet). > > On Wed, Apr 17, 2013 at 6:09 PM, Ian Price <ianpric...@googlemail.com> > wrote: > > Ian Price <ianpric...@googlemail.com> writes: > > > >> The current issues with lua vs master are as follows > >> 1) <application> has been renamed to <call> on master > >> 2) <sequence> has been replaced with <seq> which is not quite a drop-in > >> 3) while was being compiled into something with improper scoping. > >> > >> I have fixes for these locally. There is just the question of rebase vs > >> merge for bringing the branch up to date. Any preference there? > > > > Sorry, got distracted. > > Is it okay to merge master into lua, and push these three patches? > > > > -- > > Ian Price -- shift-reset.com > > > > "Programming is like pinball. The reward for doing it well is > > the opportunity to do it again" - from "The Wizardy Compiled" > > >
