Gnus development mailing list
 help / color / mirror / Atom feed
From: Bill Wohler <wohler@newt.com>
Cc: ding@gnus.org
Subject: Re: defvars at compile time
Date: Wed, 15 Mar 2006 08:49:41 -0800	[thread overview]
Message-ID: <29323.1142441381@olgas.newt.com> (raw)
In-Reply-To: <v9irqf1x1t.fsf_-_@marauder.physik.uni-ulm.de>

Reiner Steib <reinersteib+gmane@imap.cc> wrote:

> On Wed, Mar 15 2006, Bill Wohler wrote:
> 
> > Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> >> On Tue, Mar 14 2006, Bill Wohler wrote:
> [...]
> >> >   (eval-when-compile (defvar image-load-path))
> >> 
> >> Yes.  IIRC `eval-when-compile' isn't necessary:
> >
> > Thanks.
> >
> > Not necessary, but better no? Since it's only needed during compilation,
> > doesn't putting it in an eval-when-compile produce one less form to
> > evaluate during run-time? I also find it self-documenting.
> 
> ,----[ 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 should shift this to emacs-devel if more discussion is necessary
> (Mail-Followup-To: emacs-devel).

None necessary ;-).

I had missed that discussion. Vielen dank for forwarding it!

-- 
Bill Wohler <wohler@newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.



      reply	other threads:[~2006-03-15 16:49 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07  0:18 New GNOME icons Bill Wohler
2006-03-10 23:15 ` Bill Wohler
2006-03-10 23:56 ` Reiner Steib
2006-03-11  1:23   ` Bill Wohler
2006-03-11  1:29   ` Miles Bader
2006-03-11 12:48     ` Reiner Steib
2006-03-11  2:12   ` *image-load-path-for-library update Bill Wohler
2006-03-11 11:33     ` Reiner Steib
2006-03-11 22:53       ` Bill Wohler
2006-03-12  1:43       ` Bill Wohler
2006-03-12  2:00       ` Bill Wohler
2006-03-13 11:52   ` New GNOME icons Katsumi Yamaoka
2006-03-13 16:56     ` Bill Wohler
2006-03-14  5:32       ` Katsumi Yamaoka
2006-03-14  6:43         ` Bill Wohler
2006-03-14 11:57           ` Katsumi Yamaoka
2006-03-14 17:58             ` Bill Wohler
2006-03-15  1:49               ` Katsumi Yamaoka
2006-03-15  7:34                 ` Katsumi Yamaoka
2006-03-15  7:58                   ` Katsumi Yamaoka
2006-03-16  1:41                   ` gmm-image-load-path-for-library redux (was: New GNOME icons) Bill Wohler
2006-03-16  2:04                     ` gmm-image-load-path-for-library redux Katsumi Yamaoka
2006-03-16  7:24                     ` Katsumi Yamaoka
2006-03-16  8:05                       ` Bill Wohler
2006-03-16 17:41                         ` Bill Wohler
2006-03-16  1:39                 ` New GNOME icons Katsumi Yamaoka
2006-03-14 15:16           ` Reiner Steib
2006-03-14 19:29             ` Bill Wohler
2006-03-14 21:00               ` Reiner Steib
2006-03-14 21:35                 ` Bill Wohler
2006-03-15  8:58                   ` Reiner Steib
2006-03-15 12:10                   ` Reiner Steib
2006-03-15 15:42                     ` Bill Wohler
2006-03-15 16:40                       ` defvars at compile time (was: New GNOME icons) Reiner Steib
2006-03-15 16:49                         ` Bill Wohler [this message]

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=29323.1142441381@olgas.newt.com \
    --to=wohler@newt.com \
    --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).