From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: cl functions in gnus-registry.el
Date: Mon, 18 Apr 2011 11:25:54 -0500 [thread overview]
Message-ID: <87bp03h6gd.fsf@lifelogs.com> (raw)
In-Reply-To: <b4m4o5w6o05.fsf@jpl.org>
On Mon, 18 Apr 2011 16:02:18 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote:
KY> When performing `make bootstrap' on Emacs head, the byte compiler
KY> warns about cl functions used in gnus-registry.el:
KY> gnus-registry.el:MMM:NN:Warning: function `mapcan' from cl package
KY> called at runtime
KY> gnus-registry.el:985:58:Warning: function `delete*' from cl package
KY> called at runtime
Argh. I always forget not to use those! They are so convenient! Sorry.
KY> As for this, how about the attached patch?
...
KY> In addition, I got the following when compiling registry.el:
KY> registry.el:439:1:Warning: the following functions are not known to be
KY> defined: registry-lookup-secondary, registry-lookup-secondary-value,
KY> registry-size, registry-delete, registry-insert, registry-lookup,
KY> registry-lookup-breaks-before-lexbind, registry-search, registry-prune
KY> I guess surrounding all the defmethod forms with `eval-and-compile'
KY> may be a solution (see the second patch).
I agree with both patches, feel free to push them.
Thanks!
Ted
prev parent reply other threads:[~2011-04-18 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 7:02 Katsumi Yamaoka
2011-04-18 16:25 ` Ted Zlatanov [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=87bp03h6gd.fsf@lifelogs.com \
--to=tzz@lifelogs.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).