unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Declaring cl.el obsolete
Date: Fri, 24 May 2019 12:22:30 -0400	[thread overview]
Message-ID: <jwvy32v25gl.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 83woif51y8.fsf@gnu.org

>> IOW exactly what you say we should do "first", except maybe that we use
>> the term "obsoleted" instead of "deprecated".  So is the specific word
>> the source of your doubt?
> Yes.

Then let's deprecate it instead of obsolete it (with a corresponding
warning when you use it).

I personally don't care about the difference.


        Stefan
        

PS: But I'm curious why you explain why you'd prefer "deprecate" over
"obsolete"?  We usually don't really distinguish between the two,
AFAICT, since we almost never deprecate something unless it has
a replacement which causes it to be obsolete.  In this case, the reason
why we'd deprecate it is because there are alternatives we prefer, so in
this sens it's "obsolete".  Also we have infrastructure to say something
is obsolete in a "formal" way which causes corresponding messages to be
emitted when applicable, whereas we don't have such an infrastructure
for "deprecated".




  reply	other threads:[~2019-05-24 16:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23  3:26 Declaring cl.el obsolete Stefan Monnier
2019-05-23  4:47 ` Eli Zaretskii
2019-05-23 10:28   ` Noam Postavsky
2019-05-23 14:20     ` Eli Zaretskii
2019-05-24 14:28       ` Stefan Monnier
2019-05-24 15:03         ` Eli Zaretskii
2019-05-24 16:22           ` Stefan Monnier [this message]
2019-05-23  8:44 ` Lars Ingebrigtsen
2019-05-23  8:50   ` Lars Ingebrigtsen
2019-05-23 17:03     ` Romanos Skiadas
2019-05-24  1:22       ` 조성빈
2019-05-25 20:12         ` Romanos Skiadas
2019-05-23 12:15   ` Stefan Monnier
2019-05-23 15:08   ` Ken Olum
2019-05-23 15:57     ` Sam Steingold
2019-07-23 15:07 ` Stefan Monnier
2019-07-23 16:29   ` Drew Adams
2019-07-23 16:55     ` Stefan Monnier
2019-08-06  8:02   ` 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=jwvy32v25gl.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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).