Gnus development mailing list
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	ding@gnus.org, emacs-devel@gnu.org
Subject: Re: use of (defvar <foo>)
Date: Tue, 11 Apr 2006 19:31:46 +0200	[thread overview]
Message-ID: <85bqv881dp.fsf@lola.goethe.zz> (raw)
In-Reply-To: <rzqu09059e8.fsf@loveshack.ukfsn.org> (Dave Love's message of "Tue, 11 Apr 2006 18:06:55 +0100")

Dave Love <fx@gnu.org> writes:

> If the effect of the defvar on load-history has been redefined as a
> bug, the eval-when-compile wrapper does avoid a bug, and I don't see
> how it could reasonably be harmful in a future Emacs.

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.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2006-04-11 17:31 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 [this message]
2006-04-13 16:44                 ` Dave Love
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=85bqv881dp.fsf@lola.goethe.zz \
    --to=dak@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).