From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: moving more cl seq/mapping support into core
Date: Tue, 05 Oct 2010 08:07:10 -0500 [thread overview]
Message-ID: <8739skokjl.fsf@lifelogs.com> (raw)
In-Reply-To: E1P34FN-0003g1-Dn@fencepost.gnu.org
On Tue, 05 Oct 2010 05:55:45 -0400 Richard Stallman <rms@gnu.org> wrote:
RS> The fact that many programmers use cl.el is not conclusive. Those
RS> programmers won't use cl names for anything else -- others might.
My experience as a spectator has been that almost all ELisp programmers
are aware of cl.el and don't redefine its functions.
FWIW, I am strongly in favor of making cl.el a first-class citizen. The
pain of the promotion is outweighed by the benefits IMO.
RS> Meanwhile, there is a further issue. If we move these symbols into
RS> the standard Elisp, we need to document them in the Lisp Reference
RS> manual. We could certainly do that, with some work. But it would
RS> also make the Elisp manual bigger and more expensive.
I hope that's not an impediment. Maybe it can be an optional extra
volume to the ELisp manual.
Ted
next prev parent reply other threads:[~2010-10-05 13:07 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 22:48 moving more cl seq/mapping support into core MON KEY
2010-09-25 5:13 ` Leo
2010-09-25 5:58 ` Miles Bader
2010-09-25 14:42 ` Drew Adams
2010-09-25 15:07 ` Leo
2010-09-25 15:23 ` Drew Adams
2010-09-25 15:30 ` Leo
2010-09-25 15:33 ` David Kastrup
2010-09-25 15:55 ` Drew Adams
2010-09-25 15:55 ` Drew Adams
2010-09-25 16:01 ` Leo
2010-10-01 0:33 ` Daniel Colascione
2010-09-25 21:26 ` Miles Bader
2010-09-26 10:37 ` Richard Stallman
2010-09-26 13:13 ` Leo
2010-09-26 19:32 ` Miles Bader
2010-09-27 6:27 ` Richard Stallman
2010-10-01 0:28 ` Daniel Colascione
2010-10-01 3:16 ` Miles Bader
2010-10-01 20:39 ` Daniel Colascione
2010-10-02 7:12 ` David Kastrup
2010-10-03 23:15 ` Stefan Monnier
2010-10-04 17:41 ` Daniel Colascione
2010-10-05 23:32 ` Stefan Monnier
2010-10-01 11:42 ` Richard Stallman
2010-10-01 20:36 ` Daniel Colascione
2010-10-01 11:42 ` Richard Stallman
2010-10-01 20:34 ` Daniel Colascione
2010-10-01 21:12 ` Chong Yidong
2010-09-27 19:07 ` MON KEY
2010-10-02 5:35 ` MON KEY
2010-10-04 2:03 ` Richard Stallman
2010-10-04 5:51 ` MON KEY
2010-10-06 5:21 ` Richard Stallman
2010-10-09 0:29 ` MON KEY
2010-10-10 5:09 ` Richard Stallman
2010-10-04 17:33 ` Daniel Colascione
2010-10-05 9:55 ` Richard Stallman
2010-10-05 10:20 ` Helmut Eller
2010-10-05 18:27 ` Eli Zaretskii
2010-10-06 23:41 ` Richard Stallman
2010-10-07 15:04 ` Ted Zlatanov
2010-10-07 15:17 ` Karl Fogel
2010-10-09 2:13 ` Richard Stallman
2010-10-05 13:07 ` Ted Zlatanov [this message]
2010-10-06 23:41 ` Richard Stallman
2010-10-07 9:20 ` Daniel Colascione
2010-10-08 5:47 ` Richard Stallman
2010-10-05 18:26 ` Eli Zaretskii
2010-10-06 0:29 ` MON KEY
2010-10-08 2:07 ` Christian Ohler
2010-10-08 2:18 ` Miles Bader
2010-10-08 3:15 ` Christian Ohler
2010-10-06 8:04 ` Stephen J. Turnbull
2010-10-06 9:20 ` David Kastrup
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=8739skokjl.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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.