From: "D. Goel" <deego@glue.umd.edu>
Cc: emacs-devel@gnu.org
Subject: Re: defvar vs setqif..
Date: 20 May 2002 15:00:02 -0400 [thread overview]
Message-ID: <ap3vg9id4r1.fsf@poynting.umd.edu> (raw)
In-Reply-To: <87hel3sn2d.fsf@tc-1-100.kawasaki.gol.ne.jp>
> > If there was a special-form that did exactly what defvar does, hopefully
> > people would stop using defvar when they didn't mean to...
>
> The way they're using defvar is correct.
yeah, true. i didn't mean to suggest otherwise. i just mean that
defvar
>
> It would be much better to fix the definition-finding functions to
> prefer defvars that initialize the variable over those that don't, since
> the `real' definition almost always initializes the value (and should).
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...
>
> > So i was wondering is a special-form like 'setqif' could be
> > provided whose only difference from 'defvar' is in a name...
>
> That name would be wrong, because the usage of defvar you're
> complaining about doesn't set the variable at all.
but that's why i had an 'if' at the end.. to suggest that setq only if
not already defined.. else don't setq..
>
> In any case, we should just make defvar work correctly.
mean?
in any case, all this is a very 'cosmetic' issue.. no big deal if
folks didn't like the idea :)
Have a good day,
D <http://www.glue.umd.edu/~deego/>
--
next prev parent reply other threads:[~2002-05-20 19:00 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 [this message]
2002-05-20 19:24 ` Stefan Monnier
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=ap3vg9id4r1.fsf@poynting.umd.edu \
--to=deego@glue.umd.edu \
--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).