From: Dave Love <fx@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
ding@gnus.org, emacs-devel@gnu.org
Subject: Re: use of (defvar <foo>)
Date: Thu, 13 Apr 2006 17:44:58 +0100 [thread overview]
Message-ID: <rzq8xq94e7p.fsf@loveshack.ukfsn.org> (raw)
In-Reply-To: <85bqv881dp.fsf@lola.goethe.zz> (David Kastrup's message of "Tue, 11 Apr 2006 19:31:46 +0200")
David Kastrup <dak@gnu.org> writes:
> defvar is the main way to inform the system a variable could be bound
> dynamically instead of just lexically. Having it omitted on runtime
> could lead to hard to find bugs if we change to lexical binding at one
> time.
[I'll believe that when I see it (even more than Emacs 22).]
defvars are often not added with the intention of actually
distinguishing dynamic and putative lexical binding, but specifically
to suppress the compiler warning when people care. They may well not
be in the right place to signal that bindings are lexical.
If that ever becomes an issue, you need diagnostics for the existing
code which correctly (in Emacs 21) uses the guard, and for `declare',
at least.
next prev parent reply other threads:[~2006-04-13 16:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 19:24 Dave Love
2006-04-06 19:58 ` Reiner Steib
2006-04-07 11:46 ` Dave Love
2006-04-07 19:07 ` Reiner Steib
2006-04-07 20:45 ` Stefan Monnier
2006-04-07 23:48 ` Bill Wohler
2006-04-09 13:56 ` Dave Love
2006-04-09 14:02 ` David Kastrup
2006-04-11 16:45 ` Dave Love
2006-04-10 0:29 ` Stefan Monnier
2006-04-11 17:06 ` Dave Love
2006-04-11 17:31 ` David Kastrup
2006-04-13 16:44 ` Dave Love [this message]
2006-04-11 18:42 ` Stefan Monnier
2006-04-13 16:51 ` Dave Love
2006-04-08 16:17 ` Richard Stallman
2006-04-09 14:03 ` Dave Love
2006-04-11 6:28 ` Lars Magne Ingebrigtsen
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=rzq8xq94e7p.fsf@loveshack.ukfsn.org \
--to=fx@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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 NNTP newsgroup(s).