From: Drew Adams <drew.adams@oracle.com>
To: 20056@debbugs.gnu.org
Subject: bug#20056: 25.0.50; Remove non Common Lisp stuff from cl*.el libraries
Date: Sun, 8 Mar 2015 11:02:33 -0700 (PDT) [thread overview]
Message-ID: <eab917c0-2ae5-44b7-a7b1-6108b510741e@default> (raw)
In our `cl*.el' libraries we have some user-facing `cl-*' macros etc.
that do not correspond to anything in Common Lisp. This seems
misguided.
We see this in node (cl) `Modify Macros', for example:
"The following macros were invented for this package; they have no
analogues in Common Lisp."
Why add them to a package that is for Common Lisp functionality (it is
"The GNU Emacs Common Lisp emulation package") if they are not part of
Common Lisp?
This is quite misleading, and it has led some people to think that
`letf' etc. are in fact part of Common Lisp. Please consider renaming
these without the `cl-' prefix and moving them to a different library,
whose name does not start with `cl'.
In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
of 2015-02-27 on LEG570
Bzr revision: b2a590d4e3dc692a97c1b53e015b945d84b4b4c7
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --host=i686-pc-mingw32 --enable-checking=yes,glyphs'
next reply other threads:[~2015-03-08 18:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 18:02 Drew Adams [this message]
2015-03-08 18:12 ` bug#20056: 25.0.50; Remove non Common Lisp stuff from cl*.el libraries Eli Zaretskii
2015-03-08 19:06 ` Dani Moncayo
2015-03-08 20:10 ` Eli Zaretskii
2016-02-29 20:08 ` Glenn Morris
2016-02-29 20:57 ` Drew Adams
2015-03-08 18:21 ` Daniel Colascione
2015-03-08 18:46 ` Drew Adams
2015-03-08 19:11 ` Daniel Colascione
2015-03-08 21:12 ` Drew Adams
2015-03-08 21:19 ` Daniel Colascione
2015-03-08 21:31 ` Drew Adams
2015-03-09 4:52 ` Stefan Monnier
2019-08-02 12:50 ` Lars Ingebrigtsen
2019-08-03 2:49 ` Noam Postavsky
2019-08-03 7:49 ` Štěpán Němec
2019-08-03 10:30 ` Lars Ingebrigtsen
2019-08-03 12:58 ` Noam Postavsky
2019-08-03 13:16 ` Štěpán Němec
2019-08-03 21:10 ` Stefan Monnier
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=eab917c0-2ae5-44b7-a7b1-6108b510741e@default \
--to=drew.adams@oracle.com \
--cc=20056@debbugs.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).