From: Tom Tromey <tom@tromey.com>
To: "Andreas Röhler" <andreas.roehler@online.de>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: C and Emacs Lisp code parts
Date: Fri, 01 Jul 2016 21:32:48 -0600 [thread overview]
Message-ID: <87bn2gd89r.fsf@tromey.com> (raw)
In-Reply-To: <624c3d37-c829-7187-a699-7d7bbc211a20@online.de> ("Andreas \=\?utf-8\?Q\?R\=C3\=B6hler\=22's\?\= message of "Fri, 1 Jul 2016 10:03:07 +0200")
>>>>> "Andreas" == Andreas Röhler <andreas.roehler@online.de> writes:
Andreas> last years parts of C code have been switched into the Lisp
Andreas> area. There are pro and cons, the cons seems to be an easier
Andreas> maintenance, to protect against the lack of skilled C-developers.
Andreas> The backside is a general slowness, not felt in details of such a
Andreas> change, but cumulated.Would liketo see this strategy changed. Rather
Andreas> focus at a fast and small core. Reduce the rate of changes maybe. My
Andreas> preferred Emacs must not provide everything, but be quick and reliable
Andreas> and easy to extend. Emacs Lisp seen as designed for the user-space.
Another approach is to just write Emacs Lisp, and use a compiler to
translate important parts to C. I've done a lot of this work, but it
needs some love to get to the finish line.
https://github.com/tromey/el-compilador
I wrote up the result of one very simple benchmark there -- I hacked the
compiler enough to generate compile-able C.
Tom
next prev parent reply other threads:[~2016-07-02 3:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 8:03 C and Emacs Lisp code parts Andreas Röhler
2016-07-01 8:13 ` Eli Zaretskii
2016-07-01 8:39 ` Andreas Röhler
2016-07-01 9:16 ` Alan Mackenzie
2016-07-01 12:07 ` Andreas Röhler
2016-07-01 13:04 ` Eli Zaretskii
2016-07-05 22:48 ` John Wiegley
2016-07-06 7:25 ` Andreas Röhler
2016-07-06 7:31 ` Andreas Röhler
2016-07-06 15:27 ` Phillip Lord
2016-07-01 9:17 ` John Wiegley
2016-07-01 13:26 ` Andreas Röhler
2016-07-01 9:25 ` Eli Zaretskii
2016-07-01 12:25 ` Andreas Röhler
2016-07-01 13:01 ` Eli Zaretskii
2016-07-01 13:05 ` Andy Moreton
2016-07-01 15:14 ` Karl Fogel
2016-07-01 16:52 ` Andreas Röhler
2016-07-01 17:13 ` Eli Zaretskii
2016-07-01 17:36 ` Andreas Röhler
2016-07-01 17:38 ` Eli Zaretskii
2016-07-02 16:41 ` Fabrice Popineau
2016-07-02 17:16 ` Eli Zaretskii
2016-07-01 17:55 ` Alan Mackenzie
2016-07-01 18:31 ` Andreas Röhler
2016-07-01 18:57 ` Alan Mackenzie
2016-07-01 20:04 ` Andreas Röhler
2016-07-01 20:31 ` Davis Herring
2016-07-02 6:34 ` Andreas Röhler
2016-07-02 11:29 ` Paul Eggert
2016-07-05 17:02 ` Davis Herring
2016-07-05 19:35 ` Andreas Röhler
2016-07-02 6:32 ` Eli Zaretskii
2016-07-02 7:01 ` Andreas Röhler
2016-07-02 8:15 ` Eli Zaretskii
2016-07-02 3:32 ` Tom Tromey [this message]
2016-07-02 3:42 ` Clément Pit--Claudel
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bn2gd89r.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andreas.roehler@online.de \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).