From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: policy, recommendations regarding `cl-*'
Date: Tue, 25 Sep 2012 13:31:17 -0700 [thread overview]
Message-ID: <D7726115D97B4CC3A2B125AAF9EA6E79@us.oracle.com> (raw)
I have code that uses macros from cl*.el. This code needs to work with multiple
Emacs versions. It is not clear to me how, if at all, I should change it now.
NEWS provides no guidance, AFAICT. It says only this:
*** CL's main entry is now (require 'cl-lib).
`cl-lib' is like the old `cl' except that it uses the namespace cleanly,
i.e. all its definitions have the "cl-" prefix (and internal definitions use
the "cl--" prefix).
If `cl' provided a feature under the name `foo', then `cl-lib' provides it
under the name `cl-foo' instead, with the exceptions of the few definitions
that had to use `foo*' to avoid conflicts with pre-existing Elisp entities,
which have not been renamed to `cl-foo*' but just `cl-foo'.
The old `cl' is now deprecated and is just a bunch of aliases that
provide the old non-prefixed names.
That's all well and good for Emacs Dev coders, but it does not really guide
users wrt code that must work with multiple Emacs versions. And the CL manual
does not seem to reflect this change at all. At least I find no guidance there
either about this.
I would expect to see a clear explanation, with recommendations, of migration
and multiple-version support - in NEWS, preferably. That is normal for What's
New, README, or Release Changes documents for software.
For example, if I currently have (loop...), what do you recommend? Replace it
by this?
(if (fboundp 'cl-loop) (cl-loop...) (loop...))
And likewise for all the rest.
(Yes, I know that this is only a deprecation now, and not yet desupport. I
would nevertheless like to know what you recommend for supporting multiple Emacs
versions.)
next reply other threads:[~2012-09-25 20:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 20:31 Drew Adams [this message]
2012-09-25 21:01 ` policy, recommendations regarding `cl-*' Eli Zaretskii
2012-09-25 22:09 ` Drew Adams
2012-09-26 1:15 ` Stefan Monnier
2012-09-26 2:51 ` Drew Adams
2012-09-26 3:29 ` Stefan Monnier
2012-09-26 7:02 ` Bastien
2012-09-26 12:59 ` Stefan Monnier
2012-09-26 13:12 ` Bastien
2012-09-26 17:54 ` Stefan Monnier
2012-09-26 22:04 ` Bastien
2012-09-27 20:35 ` Michael Welsh Duggan
2012-09-27 22:10 ` Stefan Monnier
2012-09-29 4:15 ` Michael Welsh Duggan
2012-09-26 14:11 ` Drew Adams
2012-09-26 19:44 ` Stefan Monnier
2012-09-26 20:13 ` Drew Adams
2012-09-26 7:42 ` Eli Zaretskii
2012-09-26 13:00 ` Stefan Monnier
2012-09-26 14:11 ` Drew Adams
2012-09-26 13:37 ` Jason Rumney
2012-09-25 21:03 ` Helmut Eller
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=D7726115D97B4CC3A2B125AAF9EA6E79@us.oracle.com \
--to=drew.adams@oracle.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.