From: Noah Lavine <noah.b.lavine@gmail.com>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: guile-devel@gnu.org, joakim@verona.se
Subject: Re: ELisp?
Date: Sat, 12 Nov 2011 13:03:17 -0500 [thread overview]
Message-ID: <CA+U71=O8fZY_YbxEpSb5e-89dew4YMBnm_Y+BVytSDQWFJftxg@mail.gmail.com> (raw)
In-Reply-To: <35C54F61-5144-4C54-808C-4A430F81D8D8@raeburn.org>
> Hmm... this touches on a political issue I'd been avoiding thinking about. Namely, adding Guile to Emacs, with Guile's new FFI support, would make dynamically loading new executable code into Emacs easy, technically, including non-GPL code written specifically to extend Emacs. There's been a lot of resistance to that in the past. See for example http://lists.gnu.org/archive/html/emacs-devel/2003-07/msg00403.html .
I haven't thought about the rest of this yet, but I believe what will
happen is probably what GCC did to solve this issue. Specifically,
there is no problem loading dynamic libraries that define a symbol
"this_compiles_with_gplv3", or whatever the specific symbol name is.
And checking for such a symbol could certainly be done with Guile's
FFI.
Of course, whether Emacs wants to be able to load *other* dynamic
libraries is a different question. But Emacs would have to face this
issue with any FFI, and I think Emacs probably wants an FFI (based on
following emacs-devel and thinking about what would make things easier
for Emacs), so they can't avoid these questions anyway. So at least
Guile isn't making things worse.
Noah
prev parent reply other threads:[~2011-11-12 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 1:35 ELisp? Noah Lavine
2011-10-09 13:37 ` ELisp? joakim
2011-10-09 19:22 ` ELisp? Noah Lavine
2011-10-11 10:12 ` ELisp? Ken Raeburn
2011-11-11 9:46 ` ELisp? joakim
2011-11-12 2:13 ` ELisp? Ken Raeburn
2011-11-12 15:00 ` ELisp? joakim
2011-11-13 0:56 ` ELisp? Ken Raeburn
2011-11-12 18:03 ` Noah Lavine [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='CA+U71=O8fZY_YbxEpSb5e-89dew4YMBnm_Y+BVytSDQWFJftxg@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.org \
--cc=joakim@verona.se \
--cc=raeburn@raeburn.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).