From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: policy, recommendations regarding `cl-*'
Date: Tue, 25 Sep 2012 23:01:15 +0200 [thread overview]
Message-ID: <83pq59hl5w.fsf@gnu.org> (raw)
In-Reply-To: <D7726115D97B4CC3A2B125AAF9EA6E79@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Tue, 25 Sep 2012 13:31:17 -0700
>
> 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.)
I think, as long as you need to support versions of Emacs without
cl-lib, just leave the code as it was, i.e. use 'loop' in the above
example.
next prev parent reply other threads:[~2012-09-25 21:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 20:31 policy, recommendations regarding `cl-*' Drew Adams
2012-09-25 21:01 ` Eli Zaretskii [this message]
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
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=83pq59hl5w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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 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).