From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: monnier@iro.umontreal.ca, emacs-pretest-bug@gnu.org,
yamaoka@jpl.org, ding@gnus.org
Subject: Re: Change in bytecomp.el breaks Gnus
Date: Mon, 15 Nov 2004 17:57:52 -0600 (CST) [thread overview]
Message-ID: <200411152357.iAFNvqY06183@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1CThOu-0003T2-VW@fencepost.gnu.org> (message from Richard Stallman on Mon, 15 Nov 2004 09:00:12 -0500)
Richard Stallman wrote:
> Most "function from cl package called at runtime" seem to involve
> situations where loading the .el file loads cl, but loading the .elc
> does not.
Do `emacs -q'.
ELISP> (load "winner")
t
ELISP> (featurep 'cl)
nil
ELISP> (load "winner.el")
t
ELISP> (featurep 'cl)
t
That will always happen when the file contains:
(eval-when-compile
(require 'cl))
because the `(require cl)' is executed when the source file is loaded,
as it should be.
However, that was _not_ the cause of the compiler warning, as I
mistakenly thought.
Here is the compiler warning:
Compiling file /home/teirllm/emacscvsdir/emacs/lisp/winner.el at Mon
Nov 15 17:27:42 2004
Entering directory `/home/teirllm/emacscvsdir/emacs/lisp/'
winner.el:53:10:Warning: Function `gensym' from cl package called at runtime
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.
Adding `with-no-warnings' as below definitely gets rid of the winner
warning. I do not know whether better solutions currently being
discussed apply to this case, nor when such better solutions would be
available.
(with-no-warnings
(defsetf winner-active-region () (store)
(if (fboundp 'zmacs-activate-region)
`(if ,store (zmacs-activate-region)
(zmacs-deactivate-region))
`(setq mark-active ,store))))
One better, currently available, solution might be to put the
`with-no-warnings' around the call to `gensym' in `defsetf'. That would
seem to get rid of all similar bogus warnings.
Sincerely,
Luc.
next prev parent reply other threads:[~2004-11-15 23:57 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 [this message]
2004-11-16 1:29 ` Nick Roberts
2004-11-16 1:49 ` Luc Teirlinck
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=200411152357.iAFNvqY06183@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).