unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: nalaginrut <nalaginrut@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Guile Lua
Date: Wed, 21 Nov 2012 11:20:38 +0800	[thread overview]
Message-ID: <1353468038.5256.84.camel@Renee-desktop.suse> (raw)
In-Reply-To: <87lidxti7b.fsf@gnu.org>

On Mon, 2012-11-19 at 22:07 +0100, Ludovic Courtès wrote:
> Hi!
> 
> nalaginrut <nalaginrut@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.
> 

I switch to lua branch then compiled it and try, seems some bugs there,
it can't run successfully:
-------------------cut--------------------
scheme@(guile-user)> ,L lua
Happy hacking with Lua!  To switch back, type `,L scheme'.
lua@(guile-user)> x=1
[enter]
[enter]
[enter]
^CWhile reading expression:
ERROR: User interrupt
lua@(guile-user)> 
-------------------end--------------------

And I checked the code, it doen't use Guile inner LALR parser.
Anybody point me out what is the suggested parser implementation? The
inner scheme-LALR(which contains GLR also) or manual parser generator?
Which is better for a practical multi-lang implementation?

And is there anyone ever evaluated the efficiency about the non-scheme
language implemented within Guile? 
Anyway, this wouldn't be a big problem, since Guile could be the future
dynamic language compiler collection, it could be optimized later.

> 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’.
> 
> 





  parent reply	other threads:[~2012-11-21  3:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-17 16:30 Guile Lua Ian Price
2012-11-19  2:30 ` nalaginrut
2012-11-19 21:07   ` Ludovic Courtès
2012-11-20  4:50     ` nalaginrut
2012-11-20 11:25       ` Ian Price
2012-11-20 17:04       ` Ludovic Courtès
2012-11-21  2:40         ` nalaginrut
2012-11-21  3:20     ` nalaginrut [this message]
2012-11-21 13:25       ` Ludovic Courtès
2012-11-21 15:51         ` Stefan Israelsson Tampe
2013-01-12  8:43           ` Nala Ginrut
2013-01-12 14:37             ` Noah Lavine
2013-01-12 15:25               ` Nala Ginrut
2013-01-13 15:13             ` Ian Price
2013-01-14 20:51               ` Stefan Israelsson Tampe
2013-01-14 21:02                 ` Ian Price
2012-11-23  3:45         ` nalaginrut
2012-11-20  0:24   ` Ian Price
2012-11-20  6:12     ` Daniel Hartwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1353468038.5256.84.camel@Renee-desktop.suse \
    --to=nalaginrut@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).