From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: Miles Bader <miles@gnu.org>, emacs-devel@gnu.org
Subject: Re: defvar vs setqif..
Date: Mon, 20 May 2002 15:24:20 -0400 [thread overview]
Message-ID: <200205201924.g4KJOLh29045@rum.cs.yale.edu> (raw)
In-Reply-To: ap3vg9id4r1.fsf@poynting.umd.edu
> how can a definition-finding function tell which of the several
> defvar's it may encounter. AFAICT, there is no way for a
> definition-finding function like tag-creation-function to tell which
> is the 'defining' defvar and which is not...
There should be only one (defvar <var> <val>) form per variable.
All others should only be (defvar <var>).
Admittedly, this cannot always be done conveniently, but I don't
think the problematic cases happen often, far from it.
Do you have evidence otherwise ?
> but that's why i had an 'if' at the end.. to suggest that setq only if
> not already defined.. else don't setq..
When have you needed that ?
(I mean actual concrete examples)
Stefan
next prev parent reply other threads:[~2002-05-20 19:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-19 20:44 defvar vs setqif D. Goel
2002-05-19 20:59 ` Colin Walters
2002-05-20 0:05 ` Miles Bader
2002-05-20 19:08 ` D. Goel
2002-05-20 19:41 ` Thien-Thi Nguyen
2002-05-20 19:47 ` Stefan Monnier
2002-05-21 13:13 ` D. Goel
2002-05-20 20:05 ` Kai Großjohann
2002-05-20 21:33 ` Richard Stallman
2002-05-20 0:03 ` Miles Bader
2002-05-20 19:00 ` D. Goel
2002-05-20 19:24 ` Stefan Monnier [this message]
2002-05-20 19:40 ` D. Goel
2002-05-20 23:15 ` Miles Bader
2002-05-21 13:18 ` D. Goel
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=200205201924.g4KJOLh29045@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@gnu.org \
--cc=miles@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).