From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Wherein I argue for the inclusion of libnettle in Emacs 24.5
Date: Mon, 03 Feb 2014 22:21:50 -0500 [thread overview]
Message-ID: <jwv61ovmv91.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ha8f3jt1.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Mon, 03 Feb 2014 14:36:42 -0800")
> Emacs doesn't have a formal stable "internal ABI", anyway.
For purposes of providing encryption "subroutines", Emacs's API
has been pretty stable in this respect. I might even claim that the ABI
has been pretty stable as well.
> 1) Carthage should be destroyed
We all agree so far.
> 4) FFI is nice for proprietary products, but sub-optimal for free software
Linking Emacs at compile-time with all the libraries someone might
potentially want to use at some point, leads for example to a Debian
package that depends on umpteen libraries. It also forces people to
come and lobby here for each one of those libraries since it can only be
added to the core, thus slowing down the whole process.
The argument that "many systems don't ship with C compilers" is not
a good reason: that's just part of the problems that need to be solved
(and can be solved) when designing that FFI. I.e. the question is not
"can we solve it" but "how are we going to solve it".
> If you allow binary modules to be inserted, they aren't that useful
> unless you lock down your internal ABIs.
As mentioned, a large part of that ABI has been very stable over
the years. And we wouldn't need to freeze it for ever (e.g. require
a recompile when going from Emacs-23 to Emacs-24).
> And I think that would be a hindrance to further Emacs development.
The current situation is a hindrance to Emacs development. An FFI is
not a panacea, of course, but it at least opens up new opportunities.
Stefan
next prev parent reply other threads:[~2014-02-04 3:21 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 22:36 Wherein I argue for the inclusion of libnettle in Emacs 24.5 Lars Ingebrigtsen
2014-02-04 3:21 ` Stefan Monnier [this message]
2014-02-04 13:07 ` Ted Zlatanov
2014-02-04 14:44 ` Stephen J. Turnbull
2014-02-04 18:36 ` Ted Zlatanov
2014-02-04 22:44 ` Lars Ingebrigtsen
2014-02-05 2:28 ` Stefan Monnier
2014-02-05 2:39 ` Lars Ingebrigtsen
2014-02-05 7:00 ` Ted Zlatanov
2014-02-05 8:13 ` Stephen J. Turnbull
2014-02-05 13:41 ` Ted Zlatanov
2014-02-05 15:50 ` andres.ramirez
2014-02-05 17:00 ` chad
2014-02-05 18:55 ` Ted Zlatanov
2014-02-06 5:03 ` Stephen J. Turnbull
2014-02-06 11:49 ` Ted Zlatanov
2014-02-06 13:03 ` Stefan Monnier
2014-02-06 14:28 ` Ted Zlatanov
2014-02-06 15:05 ` Stephen J. Turnbull
2014-02-06 15:54 ` Ted Zlatanov
2014-02-07 2:06 ` Stephen J. Turnbull
2014-02-07 6:51 ` David Kastrup
2014-02-07 7:15 ` Stephen J. Turnbull
2014-02-07 8:53 ` David Kastrup
2014-02-07 10:00 ` Stephen J. Turnbull
2014-02-07 10:49 ` David Kastrup
2014-02-07 20:43 ` Stephen J. Turnbull
2014-02-07 21:42 ` Ted Zlatanov
2014-02-07 22:23 ` Stephen J. Turnbull
2014-02-07 15:30 ` Ted Zlatanov
2014-02-07 9:07 ` Daiki Ueno
2014-02-07 11:54 ` Ted Zlatanov
2014-02-08 8:11 ` Daiki Ueno
2014-02-08 16:59 ` Ted Zlatanov
2014-02-05 8:19 ` Daiki Ueno
2014-02-04 13:10 ` Ted Zlatanov
2014-02-04 16:27 ` Paul Eggert
2014-02-04 18:32 ` Ted Zlatanov
2014-02-04 19:04 ` Paul Eggert
2014-02-04 20:11 ` Ted Zlatanov
2014-02-04 21:46 ` Paul Eggert
2014-02-04 22:44 ` Ted Zlatanov
2014-02-04 22:36 ` Lars Ingebrigtsen
2014-02-05 5:11 ` Daiki Ueno
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv61ovmv91.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.