From: Grant Rettke <grettke@acm.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: guile and elisp
Date: Mon, 29 Mar 2010 13:32:55 -0500 [thread overview]
Message-ID: <756daca51003291132l3f5bbe96w5c6398a8f922fb85@mail.gmail.com> (raw)
In-Reply-To: <874ojze3q3.fsf@gnu.org>
On Mon, Mar 29, 2010 at 7:01 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> What I meant is that Scheme’s disjoint boolean type should be considered
> the Right Thing. I’d rather keep it really disjoint, at the cost of
> weaker/less trivial interop, than going the elisp road too far.
Are you guys discussing something like a foreign function interface
for Scheme to Elisp and vice versa?
Sorry for the dense question as from what I have read it started very
technical, and I am wondering what is the overarching vision.
prev parent reply other threads:[~2010-03-29 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 12:22 guile and elisp Andy Wingo
2010-03-27 13:07 ` Mark H Weaver
2010-03-27 16:54 ` Andy Wingo
2010-03-27 18:01 ` Mark H Weaver
2010-03-28 12:13 ` Andy Wingo
2010-03-29 8:42 ` Ludovic Courtès
2010-03-29 10:43 ` Andy Wingo
2010-03-29 12:01 ` Ludovic Courtès
2010-03-29 18:32 ` Grant Rettke [this message]
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=756daca51003291132l3f5bbe96w5c6398a8f922fb85@mail.gmail.com \
--to=grettke@acm.org \
--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).