From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Noah Lavine Newsgroups: gmane.lisp.guile.devel Subject: Re: Guile Lua Date: Sat, 12 Jan 2013 09:37:04 -0500 Message-ID: References: <87d2zc6vla.fsf@googlemail.com> <1353292230.5256.23.camel@Renee-desktop.suse> <87lidxti7b.fsf@gnu.org> <1353468038.5256.84.camel@Renee-desktop.suse> <87lidvhyuu.fsf@gnu.org> <1357980226.23443.44.camel@Renee-desktop.suse> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b2e0f297ee2a304d3185890 X-Trace: ger.gmane.org 1358001437 13364 80.91.229.3 (12 Jan 2013 14:37:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 12 Jan 2013 14:37:17 +0000 (UTC) Cc: =?ISO-8859-1?Q?Ludovic_Court=E8s?= , guile-devel To: Nala Ginrut Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sat Jan 12 15:37:35 2013 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Tu2DG-0008Lz-Jg for guile-devel@m.gmane.org; Sat, 12 Jan 2013 15:37:34 +0100 Original-Received: from localhost ([::1]:34878 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tu2D0-0000X7-Ah for guile-devel@m.gmane.org; Sat, 12 Jan 2013 09:37:18 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:45149) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tu2Cp-0000Wj-WB for guile-devel@gnu.org; Sat, 12 Jan 2013 09:37:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tu2Cn-0003Wo-E1 for guile-devel@gnu.org; Sat, 12 Jan 2013 09:37:07 -0500 Original-Received: from mail-da0-f53.google.com ([209.85.210.53]:46660) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tu2Cn-0003Wf-54; Sat, 12 Jan 2013 09:37:05 -0500 Original-Received: by mail-da0-f53.google.com with SMTP id x6so1182725dac.12 for ; Sat, 12 Jan 2013 06:37:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=fzaCJ4XPp0Orpfug+1HPH58A7WJnG/CjF1gAgu1gofY=; b=kcChQN4gQNGb9r1ahrnvROIWW0WNtrNr5sYZPxxHuF3+IxZFMdsDdfina3MtdRRd17 sh0N4dNpzce/BmyeNJdVXI6GhAswSMtX8K2WToztdzLzLujwjHRfJA4rEMeQVsjsS1Xp 2IbnZ6TsmCR79qGO275EUP/RU04IpkjtKow2RaIgIaTpl6OPQyk6JHqP+nwx19t29iUC DnR9HGJnu90GvMqMgmgKPeTQjeVkUDKCNLW4dgUp7ALzIJBXw/yTTAkN+2qj7vQ3Udr9 YmQpoAq+klv/v6Zd+JtUJPpBaPdsy2so8v6DxLVeM2ce7s0BLU7tpr4c88VHAXMqzph+ y3Nw== Original-Received: by 10.68.228.2 with SMTP id se2mr241138213pbc.93.1358001424228; Sat, 12 Jan 2013 06:37:04 -0800 (PST) Original-Received: by 10.68.242.73 with HTTP; Sat, 12 Jan 2013 06:37:04 -0800 (PST) In-Reply-To: <1357980226.23443.44.camel@Renee-desktop.suse> X-Google-Sender-Auth: FuD00ycC7YRw5yyi75VioEmOvp0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 209.85.210.53 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:15402 Archived-At: --047d7b2e0f297ee2a304d3185890 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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. Noah On Sat, Jan 12, 2013 at 3:43 AM, Nala Ginrut wrote: > On Wed, 2012-11-21 at 16:51 +0100, Stefan Israelsson Tampe wrote: > > Hi, > > > In terms of strategy, I think Guile=E2=80=99s focus should remain pri= marily > > 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=EF=BC=8C someone raised the topic that emerge Clisp into Guile in 20= 11, > 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=C3=A8s" : > > Hi! > > > > nalaginrut 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=3D1 > > > > 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=E2=80=99t 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=E2=80=99t quite buy the =E2=80=9Cdynamic language c= ompiler > > collection=E2=80=9D. > > 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=E2=80=99s focus should rema= in > > 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=E2=80=99. > > > > > > --047d7b2e0f297ee2a304d3185890 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I sent an email about that, but it was only an idea. I tho= ught it would be nice if we could work with the Clisp people. However, I ca= n see some barriers to actually doing that, and I don't intend to work = on it any time soon.

Noah


On Sat, Jan 12, 2013 at 3:43 AM, Nala Ginrut <n= alaginrut@gmail.com> wrote:
On Wed, 2012-11-21 at 16:5= 1 +0100, Stefan Israelsson Tampe wrote:
> Hi,
> > In terms of strategy, I think Guile=E2=80=99s focus should remain= primarily
> on
> > Scheme variants, and ELisp. =C2=A0Other language front-ends are o= f 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=EF=BC=8C someone raised the topic that emerge Clisp into Guile i= n 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=C3=A8s" <ludo@gnu.org>:
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Hi!
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 nalaginrut <nalaginrut@gmail.com> skribis:
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > I switch to lua branch then compiled = it and try, seems some
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 bugs there,
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > it can't run successfully:
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > -------------------cut---------------= -----
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > scheme@(guile-user)> ,L lua
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > Happy hacking with Lua! =C2=A0To swit= ch back, type `,L scheme'.
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > lua@(guile-user)> x=3D1
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Maybe you need a semicolon here?
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > And I checked the code, it doen't= use Guile inner LALR
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 parser.
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > Anybody point me out what is the sugg= ested parser
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 implementation?
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 (system base lalr).
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > And is there anyone ever evaluated th= e efficiency about the
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 non-scheme
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > language implemented within Guile? >
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 I don=E2=80=99t think so. =C2=A0Only the S= cheme and Emacs Lisp front-end
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 are
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 reasonably mature, anyway.
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > Anyway, this wouldn't be a big pr= oblem, since Guile could be
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 the
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > future dynamic language compiler coll= ection, it could be
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 optimized
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 > later.
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 FWIW, I don=E2=80=99t quite buy the =E2=80= =9Cdynamic language compiler
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 collection=E2=80=9D.
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Others tried this before (Parrot), with so= me success in terms
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 of
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 supported languages, but not much beyond t= hat.
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 In terms of strategy, I think Guile=E2=80= =99s focus should remain
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 primarily on
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Scheme variants, and ELisp. =C2=A0Other la= nguage front-ends are of
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 course
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 welcome, but we must keep an eye on what t= he demand is.
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Thanks,
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Ludo=E2=80=99.
>




--047d7b2e0f297ee2a304d3185890--