unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: English usage bug in bytecomp.el
Date: Wed, 9 Mar 2005 10:10:56 +1300	[thread overview]
Message-ID: <16942.5344.236292.7450@farnswood.snap.net.nz> (raw)
In-Reply-To: <877jkijf2i.fsf@olgas.newt.com>


 > That's not too bad, although I prefer the "has been" variant. Here is
 > yet another using a fairly simple past tense with a word that might
 > not be known to non-programmers:
 > 
 >   FOO was deprecated in 21.4
 > 

Yes, this a good point. Obsolete generally means that it has been removed from
the code cannot be used but the that doesn't appear to be the case
here. Deprecated (at least in the programming world/US) means that it can
still be used but it will become obsolete shortly.

Perhaps the directory emacs/lisp/obsolete should be renamed
emacs/lisp/deprecated, make-obsolete-variable -> make-deprecated-variable etc


Nick

  parent reply	other threads:[~2005-03-08 21:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 20:17 English usage bug in bytecomp.el Alan Mackenzie
2005-03-07 23:09 ` Miles Bader
2005-03-08  8:02   ` Alan Mackenzie
2005-03-08  8:49     ` Nick Roberts
2005-03-08 10:24       ` David Kastrup
2005-03-08 11:45         ` Nick Roberts
2005-03-08  9:57     ` Miles Bader
2005-03-08 10:33       ` David Kastrup
2005-03-08 15:37         ` John S. Yates, Jr.
2005-03-08 16:08       ` Bill Wohler
2005-03-08 17:26         ` Andreas Schwab
2005-03-08 21:10         ` Nick Roberts [this message]
2005-03-08 22:15         ` Miles Bader
2005-03-08 22:36           ` Bill Wohler
2005-03-09 16:59           ` Richard Stallman
2005-03-09  3:12       ` Richard Stallman
2005-03-09  9:49         ` David Kastrup
2005-03-09 10:22           ` Miles Bader
2005-03-08 13:08     ` Stefan Monnier
2005-03-09  3:12     ` Richard Stallman

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=16942.5344.236292.7450@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --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).