From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Ian Price <ianprice90@googlemail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Guile Lua
Date: Mon, 14 Jan 2013 21:51:59 +0100 [thread overview]
Message-ID: <CAGua6m04gbJPX26yX+scifCZap2k0OJg9tU+yYScuRj85nW53w@mail.gmail.com> (raw)
In-Reply-To: <87ehhp9kvj.fsf@Kagami.home>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
Hi,
To note is that in order to implement common lisp one need to bypass tree-il
and generate directly to glil, the reason is that tagbody is poorly
represented
by tree-il. If we intend to be multilingual it would be nice to be able to
effectively
represent those ideoms. Any thoughts on it?
/Stefan
On Sun, Jan 13, 2013 at 4:13 PM, Ian Price <ianprice90@googlemail.com>wrote:
> Nala Ginrut <nalaginrut@gmail.com> writes:
>
> >> 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
>
> I don't think we should get ahead of ourselves, but emacs has had some
> minor CL emulation in things like cl.el and cl-lib. I think these could
> be good test cases for the elisp support.
>
> --
> 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"
>
[-- Attachment #2: Type: text/html, Size: 1953 bytes --]
next prev parent reply other threads:[~2013-01-14 20:51 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
2013-01-13 15:13 ` Ian Price
2013-01-14 20:51 ` Stefan Israelsson Tampe [this message]
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=CAGua6m04gbJPX26yX+scifCZap2k0OJg9tU+yYScuRj85nW53w@mail.gmail.com \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ianprice90@googlemail.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).