unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58739@debbugs.gnu.org, akrl@sdf.org
Subject: bug#58739: Lack of error message about number of args (?native compilation?)
Date: Sat, 29 Oct 2022 16:04:22 +0000	[thread overview]
Message-ID: <Y11PBqZhCgvVPsQL@ACM> (raw)
In-Reply-To: <831qqqiyn0.fsf@gnu.org>

On Sat, Oct 29, 2022 at 15:48:35 +0300, Eli Zaretskii wrote:
> > Cc: 58739@debbugs.gnu.org
> > Date: Sat, 29 Oct 2022 12:04:36 +0000
> > From: Alan Mackenzie <acm@muc.de>

> > > to me this fix looks like a good idea (assuming changing the definition
> > > of MANY is acceptable).

> > We'll see what Eli says.

> About what, may I ask?

My patch for this bug.

As a quick summary, the cause of spurious warning messages in the byte
compiler was subr-arity returning (12 . many) rather than the correct
(12 . 12) for a native compiled function with exactly 12 parameters.

I've corrected this, by making subr-arity return (12 . 12), and I
committed the patch earlier on this afternoon.

In the process, MANY came to be defined to mean "has &rest parameters".

I think you'll be interested in the patch.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2022-10-29 16:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23 12:12 bug#58739: Lack of error message about number of args (?native compilation?) Alan Mackenzie
2022-10-24 16:41 ` Alan Mackenzie
2022-10-25 20:15   ` Andrea Corallo
2022-10-29 12:04     ` Alan Mackenzie
2022-10-29 12:48       ` Eli Zaretskii
2022-10-29 16:04         ` Alan Mackenzie [this message]
2022-10-31 13:15       ` Andrea Corallo
     [not found] ` <handler.58739.B.166652719021045.ack@debbugs.gnu.org>
2022-10-29 13:32   ` bug#58739: Fixed Alan Mackenzie

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=Y11PBqZhCgvVPsQL@ACM \
    --to=acm@muc.de \
    --cc=58739@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=eliz@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).