From: Nick Roberts <nickrob@snap.net.nz>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: Juanma Barranquero <lekktu@gmail.com>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Obsolete functions and variables
Date: Fri, 11 Apr 2008 11:45:50 +1200 [thread overview]
Message-ID: <18430.42670.396106.323297@kahikatea.snap.net.nz> (raw)
In-Reply-To: <47FEA27D.1050501@gmail.com>
> >> I guess the dangers generally outweigh the advantages but there's not
> >> much point in marking them obsolete if they're never going to be
> >> removed.
> >
> > I agree. I just don't expect it to happen.
>
>
> I am not sure I agree. Are not a function sometimes marked as obsolete
> because there is a new better version that works in more cases? The old
> obsolete function may still work in many cases.
Obsolete \Ob"so*lete\, a. [L. obsoletus, p. p. of obsolescere.
See {Obsolescent}.]
1. No longer in use; gone into disuse; disused; neglected;
Hmm, this is starting to sound like Monty Python's dead parrot sketch!
> Maybe a more visible warning when obsolete things are found would be
> good? (Using for example lwarn.)
How would this work? Not in some hand wavy way but with a real code
explanation.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-04-10 23:45 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 [this message]
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
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
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=18430.42670.396106.323297@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=lennart.borgman@gmail.com \
--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 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).