From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: master e971ce6: Make autoloads populate a new definition-prefixes table
Date: Thu, 26 May 2016 22:52:03 +0300 [thread overview]
Message-ID: <83twhk1tss.fsf@gnu.org> (raw)
In-Reply-To: <jwv7fegher9.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 26 May 2016 14:11:01 -0400)
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: Glenn Morris <rgm@gnu.org>, emacs-devel@gnu.org
> Date: Thu, 26 May 2016 14:11:01 -0400
>
> > w32-fns.el:245:2:Warning: set-message-beep called with 1 argument, but accepts
> > only 0
> > (All of these warnings are bogus, of course.)
>
> These are indeed bogus, but I can't imagine how they could be the result
> of my commit.
You are right. The reason is that on master 'declare-function' must
specify the full arglist of the announced function, otherwise the
byte-compiler emits this warning (I get them in quite a few files).
Is that intentional? If so, we should fix all the 'declare-function'
forms that don't already state the argument lists.
next prev parent reply other threads:[~2016-05-26 19:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160526025822.15529.80475@vcs.savannah.gnu.org>
[not found] ` <20160526025822.4D91A220153@vcs.savannah.gnu.org>
2016-05-26 15:52 ` master e971ce6: Make autoloads populate a new definition-prefixes table Glenn Morris
2016-05-26 16:44 ` Eli Zaretskii
2016-05-26 17:02 ` Glenn Morris
2016-05-26 17:58 ` Stefan Monnier
2016-05-26 18:34 ` Stefan Monnier
2016-05-26 18:11 ` Stefan Monnier
2016-05-26 19:52 ` Eli Zaretskii [this message]
2016-05-26 20:47 ` Stefan Monnier
2016-05-26 21:22 ` Michael Heerdegen
2016-05-27 2:11 ` Paul Eggert
2016-05-27 6:39 ` Eli Zaretskii
2016-05-27 15:03 ` Michael Heerdegen
2016-05-27 16:48 ` Paul Eggert
2016-05-27 18:46 ` Eli Zaretskii
2016-05-27 20:48 ` Michael Heerdegen
2016-05-27 15:14 ` Michael Heerdegen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83twhk1tss.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=rgm@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).