From: Paul Eggert <eggert@cs.ucla.edu>
To: "Andreas Röhler" <andreas.roehler@online.de>,
"Davis Herring" <herring@lanl.gov>
Cc: "Alan Mackenzie" <acm@muc.de>, "Eli Zaretskii" <eliz@gnu.org>,
"Clément Pit--Claudel" <clement.pit@gmail.com>,
emacs-devel@gnu.org
Subject: Re: C and Emacs Lisp code parts
Date: Sat, 2 Jul 2016 13:29:14 +0200 [thread overview]
Message-ID: <5777A58A.7010603@cs.ucla.edu> (raw)
In-Reply-To: <0606cae0-93b6-7e4a-c760-411326ac6970@online.de>
On 07/02/2016 08:34 AM, Andreas Röhler wrote:
> My suggestion is about re-considerating, reversing a kind of dogmatic
> pro-elisp policy - as I felt it.
Perhaps you felt more dogmatism than actually exists. As I understand
it, the attitude is more to prefer Elisp, but to use C when Elisp is not
technically feasible or when performance would be too slow in Elisp.
Some inertia is involved; when something is first written in one
language and thoroughly debugged, there is a natural and understandable
reluctance to change it to the other. So the issue typically comes up
more often when considering a new feature or a major change, and the
merits of Elisp vs C can be discussed on a change-by-change basis. If
you want this process to move forward I suggest proposing a specific
change along these lines; I think you'll find less dogmatism than the
above comment would suggest.
next prev parent reply other threads:[~2016-07-02 11:29 UTC|newest]
Thread overview: 63+ 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 ` bug#14518: " Andreas Röhler
2016-07-06 7:25 ` Andreas Röhler
2016-07-06 7:31 ` Andreas Röhler
2016-07-06 14:01 ` bug#14518: " Noam Postavsky
2016-07-06 14:52 ` Eli Zaretskii
2013-05-31 9:30 ` bug#14518: abbrev edits - delay when saving Andreas Röhler
2013-06-01 3:01 ` Leo Liu
2013-06-01 5:52 ` Andreas Röhler
2013-06-05 10:11 ` Andreas Röhler
2013-06-05 13:12 ` Stefan Monnier
2013-06-05 17:02 ` Glenn Morris
2013-06-05 17:20 ` Andreas Röhler
2013-06-07 1:43 ` Glenn Morris
2013-06-07 5:38 ` Andreas Röhler
2013-06-07 7:13 ` Glenn Morris
2013-06-07 7:41 ` Andreas Röhler
2016-07-06 15:44 ` bug#14518: C and Emacs Lisp code parts Glenn Morris
2016-07-06 16:15 ` Eli Zaretskii
2016-07-06 22:36 ` John Wiegley
2016-07-07 7:33 ` Andreas Röhler
2016-07-07 15:16 ` Eli Zaretskii
2016-07-06 16:21 ` Andreas Röhler
2016-07-06 16:37 ` Eli Zaretskii
2016-07-06 17:27 ` Andreas Röhler
2016-07-06 17:35 ` Eli Zaretskii
2016-08-05 23:38 ` bug#14518: Status: abbrev edits - delay when saving npostavs
2016-12-07 19:56 ` Glenn Morris
2016-07-06 15:27 ` C and Emacs Lisp code parts Phillip Lord
2016-07-06 15:27 ` bug#14518: " 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5777A58A.7010603@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=acm@muc.de \
--cc=andreas.roehler@online.de \
--cc=clement.pit@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=herring@lanl.gov \
/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.