From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-devel@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: master e971ce6: Make autoloads populate a new definition-prefixes table
Date: Thu, 26 May 2016 23:22:09 +0200 [thread overview]
Message-ID: <87r3copla6.fsf@web.de> (raw)
In-Reply-To: jwvr3cotun2.fsf-monnier+gmane.emacs.devel@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > 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.
>
> No, that's not intentional (at least it was originally designed so as
> to distinguish the "no arg" case from the "nil arg" case).
The reason seems to be
b4d1cd: Pacify byte-compiler for
byte-compile-macroexpand-declare-function
by Paul (CC'd). AFAIU the patch indeed doesn't distinguish "arglist ()"
and "no arglist specified" - it treats both as "arglist ()".
Paul, could you please have a look?
Thanks,
Michael.
next prev parent reply other threads:[~2016-05-26 21:22 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
2016-05-26 20:47 ` Stefan Monnier
2016-05-26 21:22 ` Michael Heerdegen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3copla6.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.