From: Nala Ginrut <nalaginrut@gmail.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Guile Lua
Date: Sat, 12 Jan 2013 23:25:17 +0800 [thread overview]
Message-ID: <1358004317.23443.114.camel@Renee-desktop.suse> (raw)
In-Reply-To: <CA+U71=OSmE_WzKfsRt+hN0O_w3hSrq6kKGKZ_meJbo=4Fs+Tyg@mail.gmail.com>
On Sat, 2013-01-12 at 09:37 -0500, Noah Lavine wrote:
> I sent an email about that, but it was only an idea. I thought it
> would be nice if we could work with the Clisp people. However, I can
> see some barriers to actually doing that, and I don't intend to work
> on it any time soon.
>
Thanks for asking that.
Anyway, we may throw it into TODO list.
I don't intend to work on it too, since Lisp is not on my hack line, I
have Scheme anyway. ;-P
>
> Noah
>
>
> On Sat, Jan 12, 2013 at 3:43 AM, Nala Ginrut <nalaginrut@gmail.com>
> wrote:
> On Wed, 2012-11-21 at 16:51 +0100, Stefan Israelsson Tampe
> wrote:
> > Hi,
> > > In terms of strategy, I think Guile’s focus should remain
> primarily
> > on
> > > Scheme variants, and ELisp. Other language front-ends are
> of course
> > > welcome, but we must keep an eye on what the demand is.
> >
> > What about common lisp is scheme a lisp or is CL a
> scheme :-)
> >
>
>
> IIRC, someone raised the topic that emerge Clisp into Guile
> in 2011,
> but what's the status now?
>
> > Anyway to support CL I would think that we need to support
> placing
> > properties
> > on symbols, e,g. currently a symbol slot is a variable, but
> to
> > effectively support CL I would go for
> > /Stefan
> >
> >
> >
> > Den 21 nov 2012 14:26 skrev "Ludovic Courtès"
> <ludo@gnu.org>:
> > Hi!
> >
> > nalaginrut <nalaginrut@gmail.com> skribis:
> >
> > > 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
> >
> > Maybe you need a semicolon here?
> >
> > > And I checked the code, it doen't use Guile inner
> LALR
> > parser.
> > > Anybody point me out what is the suggested parser
> > implementation?
> >
> > (system base lalr).
> >
> > > And is there anyone ever evaluated the efficiency
> about the
> > non-scheme
> > > language implemented within Guile?
> >
> > I don’t think so. Only the Scheme and Emacs Lisp
> front-end
> > are
> > reasonably mature, anyway.
> >
> > > Anyway, this wouldn't be a big problem, since
> Guile could be
> > the
> > > future dynamic language compiler collection, it
> could be
> > optimized
> > > later.
> >
> > FWIW, I don’t quite buy the “dynamic language
> compiler
> > collection”.
> > Others tried this before (Parrot), with some success
> in terms
> > of
> > supported languages, but not much beyond that.
> >
> > In terms of strategy, I think Guile’s focus should
> remain
> > primarily on
> > Scheme variants, and ELisp. Other language
> front-ends are of
> > course
> > welcome, but we must keep an eye on what the demand
> is.
> >
> > Thanks,
> > Ludo’.
> >
>
>
>
>
>
>
next prev parent reply other threads:[~2013-01-12 15:25 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
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 [this message]
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=1358004317.23443.114.camel@Renee-desktop.suse \
--to=nalaginrut@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=noah.b.lavine@gmail.com \
/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).