From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Juanma Barranquero <lekktu@gmail.com>,
Nick Roberts <nickrob@snap.net.nz>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Obsolete functions and variables
Date: Fri, 11 Apr 2008 16:26:05 +0900 [thread overview]
Message-ID: <87r6dcq2cy.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <jwvod8hduqs.fsf-monnier+emacs@gnu.org>
Stefan Monnier writes:
> Usually, we look at the obsolete vars&funs, select the really old ones
> (e.g. the ones that are obsolete since 20.7 or maybe even 21.1) and then
> check which of these can be safely removed.
FWIW Python has been successfully deprecating and removing identifiers
for about a decade. They warn for maybe one or two release cycles
(ie, in an x.y.z scheme, from x.y.z to x.y+2.0), then the obsolete
name gets a one-way ticket to a senior community in Arizona.
However, they also support a full release cycle older than the current
release, plus security updates (source-only) for two release cycles
before that.
next prev parent reply other threads:[~2008-04-11 7:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 5:02 Obsolete functions and variables Nick Roberts
2008-04-10 10:10 ` Juanma Barranquero
2008-04-10 15:31 ` Richard Stallman
2008-04-10 15:43 ` Juanma Barranquero
2008-04-10 22:53 ` Nick Roberts
2008-04-10 23:16 ` Juanma Barranquero
2008-04-10 23:27 ` Lennart Borgman (gmail)
2008-04-10 23:45 ` Nick Roberts
2008-04-11 0:21 ` Lennart Borgman (gmail)
2008-04-11 1:20 ` Mike Mattie
2008-04-11 1:17 ` Mike Mattie
2008-04-11 1:53 ` Stefan Monnier
2008-04-11 7:26 ` Stephen J. Turnbull [this message]
2008-04-12 0:10 ` Richard Stallman
2008-04-12 0:58 ` Sebastian Rose
2008-04-12 1:02 ` Nick Roberts
2008-04-12 5:34 ` Stefan Monnier
2008-04-12 10:06 ` Nick Roberts
2008-04-12 13:38 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r6dcq2cy.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=nickrob@snap.net.nz \
--cc=rms@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.