Gnus development mailing list
 help / color / mirror / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-pretest-bug@gnu.org, yamaoka@jpl.org,
	monnier@iro.umontreal.ca, ding@gnus.org
Subject: Re: Change in bytecomp.el breaks Gnus
Date: Mon, 15 Nov 2004 19:49:38 -0600 (CST)	[thread overview]
Message-ID: <200411160149.iAG1ncS09476@raven.dms.auburn.edu> (raw)
In-Reply-To: <16793.22523.422716.335788@farnswood.snap.net.nz> (message from Nick Roberts on Tue, 16 Nov 2004 14:29:31 +1300)

Nick Robert wrote:

    > This warning is bogus.  `gensym' can indeed be called at runtime, but
    > only if `setf' is called first, which requires cl to be loaded anyway.

   I don't think this is bogus. setf is a macro and is not needed at runtime
   because it has been expanded and compiled into winner.elc (I think you might
   mean defsetf but that is also a macro, so the same applies). gensym, on the
   other hand, is a function, so Emacs will need to know where to find it
   when it is called.

I do not believe so.  The only purpose of defsetf is to tell setf what
to do.  The expansion of the defsetf macro will only be called if setf
is called first, which requires cl to be loaded.  _No_ cl function
used inside the defsetf expansion will ever load cl, when called from
there.

Sincerely,

Luc.

  reply	other threads:[~2004-11-16  1:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877jouepy8.fsf@telia.com>
     [not found] ` <b9yd5ymkq11.fsf@jpl.org>
2004-11-11  7:40   ` Katsumi Yamaoka
2004-11-11 11:18     ` Katsumi Yamaoka
2004-11-11 17:45       ` Luc Teirlinck
2004-11-11 21:55         ` Stefan
2004-11-11 22:41           ` Luc Teirlinck
2004-11-11 22:54             ` Luc Teirlinck
2004-11-12  0:22           ` Katsumi Yamaoka
2004-11-12  3:57             ` Stefan Monnier
2004-11-12  4:30               ` Katsumi Yamaoka
2004-11-13 23:03                 ` Stefan
2004-11-14  0:14                   ` Katsumi Yamaoka
2004-11-14  5:21                     ` Stefan
2004-11-14  6:10                       ` Katsumi Yamaoka
2004-11-14  6:36                         ` Stefan
2004-11-14 13:44                           ` Katsumi Yamaoka
2004-11-14 17:29                         ` Luc Teirlinck
2004-11-14 19:17                           ` Stefan Monnier
2004-11-15 14:00                             ` Richard Stallman
2004-11-15 15:36                               ` Stefan Monnier
2004-11-15 23:22                                 ` Miles Bader
2004-11-15 23:28                                   ` Stefan Monnier
2004-11-15 23:38                                     ` Miles Bader
2004-11-15 23:44                                       ` Stefan Monnier
2004-11-15 23:57                               ` Luc Teirlinck
2004-11-16  1:29                                 ` Nick Roberts
2004-11-16  1:49                                   ` Luc Teirlinck [this message]
2004-11-16  2:19                                   ` Luc Teirlinck
2004-11-16 16:49                           ` Richard Stallman

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=200411160149.iAG1ncS09476@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=ding@gnus.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=yamaoka@jpl.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).