From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: ding@gnus.org
Subject: Re: use of (defvar <foo>)
Date: Thu, 06 Apr 2006 21:58:16 +0200 [thread overview]
Message-ID: <v9fykq8oiv.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <rzqfykqo6cu.fsf@loveshack.ukfsn.org> (Dave Love's message of "Thu, 06 Apr 2006 20:24:01 +0100")
On Thu, Apr 06 2006, Dave Love wrote:
> Gnus has lots of instances of `(defvar <foo>)' that aren't protected
> by `eval-when-compile' and should be.
I learned on emacs-devel that we don't need `eval-when-compile' in
this case (unless I'm misunderstanding what you are referring to):
,----[ http://article.gmane.org/gmane.emacs.devel/42998 ]
| From: Stefan Monnier
| Subject: Re: defvars at compile time
|
| [...]
|
| The form (defvar foo) was specifically designed as a byte-compiler
| directive, so please make use of it.
`----
,----[ http://article.gmane.org/gmane.emacs.devel/43027 ]
| From: Richard M. Stallman
| Subject: Re: defvars at compile time
|
| The only effect of a defvar with no initial value
| is to silence the compiler. So it is superfluous
| to put it inside eval-when-compile.
`----
We had this discussion about it recently:
http://thread.gmane.org/gmane.emacs.devel/51304/focus=11990
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-04-06 19:58 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 [this message]
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
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=v9fykq8oiv.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.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.
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).