From: Nicolas Petton <petton.nicolas@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: sequence manipulation functions
Date: Wed, 05 Nov 2014 18:41:12 +0100 [thread overview]
Message-ID: <874mudilzb.fsf@gmail.com> (raw)
In-Reply-To: <f1462510-edda-4984-9dce-e369790ec529@default>
I see "cl-lib" as a compatibility package with Common Lisp, not a base
library of the language. My goal is not to remove or replace "cl-lib",
but to add core sequence functions to Elisp.
Nico
Drew Adams <drew.adams@oracle.com> writes:
>> I think these should use a "seq-" prefix. This will not only avoid
>> naming conflicts, but also helps discover those functions, since you
>> can type `(seq- TAB' to see all related functions.
>
> No. Emacs should follow Common Lisp in this regard.
> http://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node141.html#SECTION001800000000000000000
>
> And it should follow it not only in terms of names but also in terms
> of behavior, as much as is practical. E.g., `some-p' should be `some',
> and it should have the Common Lisp `some' behavior.
>
> This might already be more or less the case for `cl-some' etc., in
> which case there is no need (and it would be a nuisance) to add a
> separate `some-p' etc. with a different behavior.
--
Nicolas Petton
http://nicolas-petton.fr
next prev parent reply other threads:[~2014-11-05 17:41 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 22:17 sequence manipulation functions Nicolas Petton
2014-11-05 1:21 ` Glenn Morris
2014-11-05 9:46 ` Nicolas Petton
2014-11-05 4:58 ` Richard Stallman
2014-11-05 9:45 ` Nicolas Petton
2014-11-06 0:54 ` Daniel Colascione
2014-11-05 9:23 ` Damien Cassou
2014-11-05 18:12 ` Richard Stallman
2014-11-05 21:59 ` Nicolas Petton
2014-11-05 22:40 ` Stefan Monnier
2014-11-06 0:30 ` Richard Stallman
2014-11-05 15:26 ` Stefan Monnier
2014-11-05 15:36 ` Nicolas Petton
2014-11-05 15:52 ` Sebastien Vauban
2014-11-05 18:32 ` Stefan Monnier
2014-11-07 17:35 ` [PATCH] " Nicolas Petton
2014-11-07 17:43 ` Daniel Colascione
2014-11-10 17:41 ` Stefan Monnier
2014-11-10 22:28 ` Nicolas Petton
2014-11-10 23:12 ` Nicolas Petton
2014-11-11 2:20 ` Stefan Monnier
2014-11-12 17:49 ` Nicolas Petton
2014-11-12 19:12 ` Bozhidar Batsov
2014-11-12 19:30 ` Nicolas Petton
2014-11-12 20:28 ` Stefan Monnier
2014-11-12 20:56 ` Nicolas Petton
2014-11-12 23:06 ` Nicolas Petton
2014-11-12 23:17 ` Nic Ferrier
2014-11-13 1:29 ` Leo Liu
2014-11-13 5:21 ` Drew Adams
2014-11-14 5:16 ` Leo Liu
2014-11-16 12:52 ` Bozhidar Batsov
2014-11-16 14:16 ` Nicolas Petton
2014-11-16 17:22 ` Drew Adams
2014-11-16 19:13 ` Stefan Monnier
2014-11-17 2:52 ` Richard Stallman
2014-11-17 11:46 ` Nicolas Petton
2014-11-17 13:53 ` Stefan Monnier
2014-11-16 7:38 ` Damien Cassou
2014-11-20 23:16 ` Stefan Monnier
2014-11-21 12:40 ` Nicolas Petton
2014-11-21 13:11 ` Stefan Monnier
2014-11-21 13:28 ` Nicolas Petton
2014-11-21 14:44 ` Stefan Monnier
2014-11-24 17:49 ` Nicolas Petton
2014-11-24 18:01 ` Nicolas Petton
2014-11-05 16:25 ` Drew Adams
2014-11-05 17:21 ` Artur Malabarba
2014-11-05 18:27 ` Drew Adams
2014-11-05 17:22 ` Damien Cassou
2014-11-05 18:28 ` Drew Adams
2014-11-05 17:41 ` Nicolas Petton [this message]
2014-11-05 18:23 ` Tom Tromey
2014-11-05 18:29 ` Drew Adams
2014-11-05 18:29 ` Drew Adams
2014-11-06 4:39 ` Richard Stallman
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=874mudilzb.fsf@gmail.com \
--to=petton.nicolas@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).