all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
Subject: argument names for define-obsolete-*-alias
Date: Mon, 13 Jun 2005 01:30:12 +0200	[thread overview]
Message-ID: <f7ccd24b0506121630605be81a@mail.gmail.com> (raw)

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.

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?

-- 
                    /L/e/k/t/u

             reply	other threads:[~2005-06-12 23:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-12 23:30 Juanma Barranquero [this message]
2005-06-13  0:43 ` argument names for define-obsolete-*-alias Nick Roberts
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7ccd24b0506121630605be81a@mail.gmail.com \
    --to=lekktu@gmail.com \
    /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.