unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: RE: Rationalising c[ad]\{2,5\}r.
Date: Thu, 12 Mar 2015 07:03:11 -0700 (PDT)	[thread overview]
Message-ID: <0de5f80c-c3ef-4688-a558-d3f935c2c2dd@default> (raw)
In-Reply-To: <20150312103014.GB2625@acm.fritz.box>

> > > and there will be compatibility aliases for cl-caaadr etc..
> 
> > Why? Why is that needed?
> 
> Because there are lots of uses of cl-c[ad]\{3,4\}r in the field.  There
> are currently 56 uses in the Emacs sources, which we could easily fix,
> but there will be an unknown, possibly high, number in packages and code
> we don't control.  It would be ill-mannered simply to remove these names.
> They should be marked as obsolete, perhaps.

See my reply to Artur/Bruce.  I meant only that the `cl-' versions are
not needed.  We should definitely not remove the c[ad]\{3,4\}r.

If there are already "lots of" cl-c[ad]\{3,4\}r in the field, then
that would be too bad.  But I doubt that that is the case.

Occurrences of such barbarities would, I expect, represent only the
exceptional overzealous, early-adopter, conversion of *existing*
c[ad]\{3,4\}r.  The 56 uses in the Emacs sources are in fact a case
in point.  Who would write (cl-cadddr (cl-cdar x)) in new code?
 
And even if it is case that there are "lots of" such occurrences out
there, we should just apologize for our recent-past silliness, redefine
the cl-c[ad]\{3,4\}r as temporary (only) aliases for c[ad]\{3,4\}r,
deprecate those aliases, and remove them as soon as possible thereafter.

I would be quite surprised if there are really a lot of cl-c[ad]\{3,4\}r
out there.  But there are no doubt lots of c[ad]\{3,4\}r out there.



  reply	other threads:[~2015-03-12 14:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 21:43 Rationalising c[ad]\{2,5\}r Alan Mackenzie
2015-03-11 22:00 ` Drew Adams
2015-03-11 22:54   ` Artur Malabarba
2015-03-12  1:51     ` Drew Adams
2015-03-12  9:54       ` Artur Malabarba
2015-03-12 14:01         ` Drew Adams
2015-03-12  4:34     ` Stephen J. Turnbull
2015-03-12 10:15       ` Artur Malabarba
2015-03-12 10:30   ` Alan Mackenzie
2015-03-12 14:03     ` Drew Adams [this message]
2015-03-11 22:15 ` Thien-Thi Nguyen
2015-03-11 23:00   ` Alan Mackenzie
2015-03-11 23:36     ` Thien-Thi Nguyen
2015-03-12  1:35       ` Samuel W. Flint
2015-03-12  0:52     ` Artur Malabarba
2015-03-12  8:56       ` Alan Mackenzie
2015-03-12 10:15         ` Artur Malabarba
2015-03-12 13:53     ` Stefan Monnier
2015-03-13 16:41       ` Alan Mackenzie
2015-03-13 16:47         ` Drew Adams
2015-03-13 20:38         ` Stefan Monnier
2015-03-13 21:36           ` Alan Mackenzie
2015-03-13 23:00             ` Stefan Monnier
2015-04-05 13:00               ` Alan Mackenzie

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=0de5f80c-c3ef-4688-a558-d3f935c2c2dd@default \
    --to=drew.adams@oracle.com \
    --cc=acm@muc.de \
    --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).