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: argument names for define-obsolete-*-alias
Date: Mon, 13 Jun 2005 12:43:55 +1200	[thread overview]
Message-ID: <17068.54987.233487.611012@farnswood.snap.net.nz> (raw)
In-Reply-To: <f7ccd24b0506121630605be81a@mail.gmail.com>

 > Is everybody happy with the names of the `make-obsolete*' and
 > `define-obsolete-*-alias' arguments?
 > 
 > The alias being created is called FUNCTION or VARIABLE, and the symbol
 > (or definition) being aliased, NEW. Now, I understand the rationale:
 > NEW because it is the new, shinier name.
 > 
 > However, and even knowing as I know that all defining functions and
 > macros get the defined symbol as first argument, today I tried to use
 > `define-obsolete-variable-name' and on first reading of the docstring
 > I just put the arguments reversed. From the Emacs history POV, NEW is
 > indeed newer; from the use case of define-obsolete*, however, NEW is
 > "old" because it already exists.

NEW is an argument, not part of the function name, so I wouldn't expect
it to create a new symbol. These functions/macros are also defined in
XEmacs with similar argument names which makes it clearer that they
really do the same thing.

 > Wouldn't be better to use OBSOLETE and CURRENT (or MODERN), or ALIAS
 > and ORIGINAL, or some other pair that best defines the relationship
 > between the arguments?

I think these are confusing. OBSOLETE and CURRENT would only be 
obsolete and current _after_ the function/macro has been evaluated.
Maybe FROM and TO would work. 

On a related note, I find the arguments for defvaralias and defalias more
confusing than those for define-obsolete-*-alias.

Nick

  reply	other threads:[~2005-06-13  0:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-12 23:30 argument names for define-obsolete-*-alias Juanma Barranquero
2005-06-13  0:43 ` Nick Roberts [this message]
2005-06-13  1:00   ` Juanma Barranquero
2005-06-13 17:37     ` Daniel Brockman
2005-06-13 23:38   ` Richard Stallman
2005-06-13 23:38 ` Richard Stallman
2005-06-14  0:16   ` Juanma Barranquero
2005-06-14  7:27     ` David Kastrup
2005-06-14  9:08       ` Juanma Barranquero
2005-06-14  9:16         ` David Kastrup
2005-06-15 14:46       ` Richard Stallman
2005-06-15 14:57         ` Juanma Barranquero
2005-06-15 21:13           ` Nick Roberts
2005-06-15 23:20             ` Juanma Barranquero

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=17068.54987.233487.611012@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).