From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: Why aren't `find`, `find-if`, `remove-if` part of Emacs Lisp?
Date: Tue, 24 Jun 2014 12:24:25 -0400 [thread overview]
Message-ID: <barmar-6EDEC1.12242524062014@news.eternal-september.org> (raw)
In-Reply-To: wfker42etnyi.fsf@sap.com
In article <wfker42etnyi.fsf@sap.com>,
Christoph Wedler <christoph.wedler@sap.com> wrote:
> To be honest, I do not fully understand why Emacs has such an anti-CL
> policy.
Basically, RMS thinks CL is too bloated. From
http://www.gnu.org/gnu/rms-lisp.html:
Obviously, machines are bigger now, and we don't do it that way any
more. We put in 'caar' and 'cadr' and so on, and we might put in another
looping construct one of these days. We're willing to extend it some
now, but we don't want to extend it to the level of common Lisp. I
implemented Common Lisp once on the Lisp machine, and I'm not all that
happy with it. One thing I don't like terribly much is keyword arguments
(8). They don't seem quite Lispy to me; I'll do it sometimes but I
minimize the times when I do that.
Footnote (8) says:
I don't mind if a very complex and heavyweight function takes keyword
arguments. What bothers me is making simple basic functions such as
"member" use them.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
next prev parent reply other threads:[~2014-06-24 16:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 17:13 Why aren't `find`, `find-if`, `remove-if` part of Emacs Lisp? Nicolas Petton
2014-06-17 17:28 ` Stefan Monnier
2014-06-17 18:36 ` Nicolas Petton
2014-06-17 18:56 ` Doug Lewan
2014-06-17 19:06 ` Nicolas Petton
2014-06-17 19:55 ` Doug Lewan
2014-06-17 22:16 ` Stefan Monnier
2014-06-18 11:00 ` Nicolas Petton
[not found] ` <mailman.3879.1403089222.1147.help-gnu-emacs@gnu.org>
2014-06-18 14:36 ` Stefan Monnier
2014-06-18 14:43 ` Barry Margolin
2014-06-18 15:43 ` Damien Cassou
2014-06-18 16:31 ` Phillip Lord
[not found] ` <mailman.3896.1403106263.1147.help-gnu-emacs@gnu.org>
2014-06-24 13:51 ` Christoph Wedler
2014-06-24 16:24 ` Barry Margolin [this message]
2014-06-25 3:22 ` Stefan Monnier
2014-06-25 4:08 ` Leo Liu
[not found] ` <mailman.4252.1403669342.1147.help-gnu-emacs@gnu.org>
2014-06-25 13:46 ` Stefan Monnier
[not found] ` <mailman.4251.1403666567.1147.help-gnu-emacs@gnu.org>
2014-06-25 10:24 ` Christoph Wedler
2014-06-25 13:35 ` Stefan Monnier
2014-06-25 14:09 ` Stefan Monnier
2014-06-25 15:37 ` Barry Margolin
2014-06-25 23:44 ` Robert Thorpe
2014-06-18 14:43 ` Pascal J. Bourguignon
[not found] ` <mailman.3837.1403026153.1147.help-gnu-emacs@gnu.org>
2014-06-20 0:20 ` WJ
2014-06-20 13:45 ` Stefan Monnier
[not found] <mailman.3836.1403025251.1147.help-gnu-emacs@gnu.org>
2014-06-17 21:42 ` Barry Margolin
[not found] <mailman.4322.1403739913.1147.help-gnu-emacs@gnu.org>
2014-06-26 0:37 ` Stefan Monnier
2014-06-26 5:27 ` Barry Margolin
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=barmar-6EDEC1.12242524062014@news.eternal-september.org \
--to=barmar@alum.mit.edu \
--cc=help-gnu-emacs@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.