On Mon, 2012-11-19 at 22:07 +0100, Ludovic Courtès wrote: > Hi! > > nalaginrut <nalagin...@gmail.com> skribis: > > > I'd like to know what work should the maintainer take? As I know there's > > some work has been done, but it didn't merge into stable-2.0. What's the > > rest work? Does it work now? > > I think the first task for you (congratulations! ;-)) or anyone else > interested will be to check out the branch, build it, assess it, and > tell us what it’s current status is. > > Then, assuming it’s in a good shape, one would have to try running > actual Lua programs, in search of bugs. Along the way, these bugs would > have to be fixed, and the test suite augmented accordingly. > > Then the fine points regarding multi-language integration will have to > be sorted out. The manual will have to be updated. > > When all this is in place, we can consider merging the branch. I > wouldn’t want to merge a half-baked front-end. > > WDYT? > > Ludo’. > >
@ijp: thanks for the info ;-) @ludo: Thanks! I'll try to do it follow your steps. Besides, do we have the final conclusion for the multi-lang choosing approach, say, --lang=lua/elisp or #lang lua or a script: guile-lua/guile-elisp... whatever. IIRC, ijp raised such a topic, but it seems no conclusion. I ask this because there should be an easy way to test some big code segment written in other language.
