From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: defvaralias
Date: Sat, 7 May 2005 13:19:58 +1200 [thread overview]
Message-ID: <17020.6078.335703.434592@farnswood.snap.net.nz> (raw)
In-Reply-To: <200505061456.j46EuMh11458@raven.dms.auburn.edu>
Luc Teirlinck writes:
> Nick Roberts wrote:
>
> > (defvar var1 "DOC1")
> > (defvar var2 "DOC2")
> > (defvaralias 'var1 'var2)
>
> I think if an alias is made only then only one of the variables needs to be
> declared.
>
> So the idea of the present behavior would be to do a
> (defvaralias 'var1 'var2) with a defvar for var1 instead of for var2?
> I do not believe that would be appropriate.
I mean:
(defvar var2 "DOC2")
(defvaralias 'var1 'var2)
is doesn't give compiler warnings. Presumably defvaralias is a declaration
for var1.
> As Stefan has pointed out defvaralias has a symmetry in its
> arguments (unlike define-obsolete-variable-alias neither)
>
> I do not understand. The variable alias structure is a directed
> graph, not an undirected graph. The arguments to defvaralias are
> asymmetric in their meaning. The first argument is the alias, the
> second the base variable.
>
> (defvaralias 'var1 'var2)
>
> is different (in non-trivial ways) from
>
> (defvaralias 'var2 'var1)
>
Yes, you're right and I'm misquoting Stefan. There must be some symmetry,
however as:
(defvar var2 "DOC2")
(defvaralias 'var1 'var2)
(defvar var1a "DOC1")
(defvaralias 'var1a 'var2a)
doesn't give compiler warnings either.
Nick
> in as far as `indirect-variable', cyclic variable indirection errors
> and such are concerned.
>
> Sincerely,
>
> Luc.
next prev parent reply other threads:[~2005-05-07 1:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 1:42 defvaralias Luc Teirlinck
2005-05-06 2:01 ` defvaralias Luc Teirlinck
2005-05-06 4:30 ` defvaralias Nick Roberts
2005-05-06 14:56 ` defvaralias Luc Teirlinck
2005-05-07 1:19 ` Nick Roberts [this message]
2005-05-07 1:32 ` defvaralias Luc Teirlinck
2005-05-07 15:11 ` defvaralias Stefan Monnier
2005-05-07 15:33 ` defvaralias Luc Teirlinck
2005-05-07 15:39 ` defvaralias Luc Teirlinck
2005-05-07 18:35 ` defvaralias Richard Stallman
2005-05-06 15:43 ` defvaralias Luc Teirlinck
2005-05-06 18:51 ` defvaralias Richard Stallman
2005-05-06 22:39 ` defvaralias Luc Teirlinck
2005-05-07 18:35 ` defvaralias Richard Stallman
2005-05-07 18:44 ` defvaralias Luc Teirlinck
2005-05-07 19:31 ` defvaralias Luc Teirlinck
2005-05-07 20:09 ` defvaralias Juanma Barranquero
2005-05-07 20:54 ` defvaralias Luc Teirlinck
2005-05-07 20:04 ` defvaralias Juanma Barranquero
2005-05-08 16:11 ` defvaralias Richard Stallman
2005-05-08 16:41 ` defvaralias Luc Teirlinck
2005-05-07 9:26 ` defvaralias Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2003-10-28 1:25 defvaralias Luc Teirlinck
2003-10-28 2:08 ` defvaralias Miles Bader
2003-10-28 2:29 ` defvaralias Luc Teirlinck
2003-10-29 19:02 ` defvaralias 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=17020.6078.335703.434592@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).