From: Eli Zaretskii <eliz@gnu.org>
To: "Jean Louis" <bugs@rcdrun.com>
Cc: 58319@debbugs.gnu.org
Subject: bug#58319: 29.0.50; Not logical compilation warnings
Date: Thu, 06 Oct 2022 08:33:15 +0300 [thread overview]
Message-ID: <837d1dsehw.fsf@gnu.org> (raw)
In-Reply-To: <86o7uq5ds3.fsf@protected.rcdrun.com> (bugs@rcdrun.com)
> From: "Jean Louis" <bugs@rcdrun.com>
> Date: Wed, 05 Oct 2022 21:25:00 +0300
>
>
> I am testing new function M-x emacs-lisp-native-compile-and-load
> and I can see some new warnings that I have not seen before.
The aspects of the warnings you are asking about have nothing to do
with native-compilation, the warnings are emitted by the byte
compiler.
> These warnings are not enlightening neither helpful.
Maybe you need to get used to what they say, that's all.
> It is not clear what the sign + after number means. It is unclear if it
> means "5 and more" or "more than five". That sign is not helpful.
It means 5 or more. Usually, it means the function's signature has 5
mandatory arguments and then something like "&rest args".
> To me it looks same 5+ and 5-10, as both mean to me that it is 5 and
> more arguments. But maybe author wants to say what it should mean.
Emacs can only say "5-10" when the function uses &optional, because
only in that case it is possible to know how many more can follow.
I think this format of warnings exists since about forever.
next prev parent reply other threads:[~2022-10-06 5:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 18:25 bug#58319: 29.0.50; Not logical compilation warnings Jean Louis
2022-10-06 5:33 ` Eli Zaretskii [this message]
2022-10-06 10:06 ` Jean Louis
2022-10-06 10:54 ` Mattias Engdegård
2022-10-06 12:22 ` Lars Ingebrigtsen
2022-10-07 11:00 ` Jean Louis
2022-10-07 12:07 ` Mattias Engdegård
2022-10-07 10:58 ` Jean Louis
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=837d1dsehw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58319@debbugs.gnu.org \
--cc=bugs@rcdrun.com \
/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.