From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 14734@debbugs.gnu.org
Subject: bug#14734: 24.3.50; REGRESSION: defadvice broken wrt doc strings (C-h f)
Date: Fri, 28 Jun 2013 19:28:35 -0700 (PDT) [thread overview]
Message-ID: <49fae9c3-c59c-4b08-84f0-24dc9935b345@default> (raw)
In-Reply-To: <jwvr4fl1xfm.fsf-monnier+emacs@gnu.org>
> >> > Let me add that advice.el is not yet obsolete,
> >> Indeed, but it's only a question of time.
> > So much for the argument about "backward compatibility".
>
> What kind of ass comment is that?
?
> You know full well that "obsolete" does not mean "not backward
> compatible".
An argument was made that the REimplementation of something that
worked well was done (was necessary?) to allow for backward
compatibility. I was speaking to that argument.
If that is really the reason for reimplementing the old, and
the old is slated for obsolescence, then that extra "backward
compatibility" work, which degrades the user experience, would
not seem to be worth much, would it?
I have my doubts that providing "backward compatibility" was
the reason for the reimplementation, but I have no special
insight into the reason. Clearly, someone went to some trouble
to code the old anew, for some reason.
The old code was already backward compatible, by definition.
What was the reason that the `C-h f' behavior needed to change
so negatively? Please don't say that it is a gift of backward
compatibility.
next prev parent reply other threads:[~2013-06-29 2:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 17:08 bug#14734: 24.3.50; REGRESSION: defadvice broken wrt doc strings (C-h f) Drew Adams
2013-06-27 18:15 ` Stefan Monnier
2013-06-27 18:40 ` Drew Adams
2013-06-28 17:39 ` Drew Adams
2013-06-28 20:44 ` Dmitry Gutov
2013-06-28 21:56 ` Drew Adams
2013-06-28 22:19 ` Michael Heerdegen
2019-09-23 21:07 ` bug#13581: " Lars Ingebrigtsen
2013-06-28 22:27 ` Michael Heerdegen
2013-06-28 23:21 ` Stefan Monnier
2013-06-29 1:37 ` Drew Adams
2013-06-29 2:09 ` Stefan Monnier
2013-06-29 2:28 ` Drew Adams [this message]
2013-06-29 3:24 ` Stefan Monnier
2013-06-29 20:29 ` Juanma Barranquero
2013-06-30 1:39 ` Stefan Monnier
2013-07-05 14:50 ` Drew Adams
2013-07-05 14:57 ` Juanma Barranquero
2013-07-05 22:44 ` Stefan Monnier
2013-07-06 1:40 ` Drew Adams
2013-07-06 9:18 ` Stefan Monnier
2013-07-06 20:22 ` Drew Adams
2013-10-20 23:27 ` Drew Adams
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=49fae9c3-c59c-4b08-84f0-24dc9935b345@default \
--to=drew.adams@oracle.com \
--cc=14734@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--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).