From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: guile and elisp
Date: Mon, 29 Mar 2010 10:42:27 +0200 [thread overview]
Message-ID: <87tyrzfrik.fsf@gnu.org> (raw)
In-Reply-To: m3bpectwu6.fsf@pobox.com
Hello Guilemacsers! :-)
Not sure about the fine technical points, but I think the general
philosophy should consider these points:
- There’s currently no Scheme code that interacts with Elisp. Thus,
code that will be written specifically to interact with Elisp code
can adjust to do the right thing, e.g., make explicit calls to
‘canonicalize-boolean’, etc., as Mark suggested.
- Scheme’s #f/() are more expressive that elisp’s nil. They can be
easily mapped to nil, whereas it seems hard to automatically choose
whether to map nil to #f or to (). This also supports the idea of
requiring Scheme code to make explicit conversions.
- Elisp should be considered “legacy”. Whenever something can’t be
made transparent, I’d consider Scheme first-class and Elisp
second-class.
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-03-29 8:42 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 [this message]
2010-03-29 10:43 ` Andy Wingo
2010-03-29 12:01 ` Ludovic Courtès
2010-03-29 18:32 ` Grant Rettke
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=87tyrzfrik.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).