unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 12299@debbugs.gnu.org
Subject: bug#12299: 24.1; no byte compiler warning for inline function call with too few arguments
Date: Fri, 16 Aug 2019 15:46:52 -0700	[thread overview]
Message-ID: <8736i0ohib.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87ligyqwb5.fsf@gnu.org> (Roland Winkler's message of "Tue, 28 Aug 2012 21:14:06 -0500")

"Roland Winkler" <winkler@gnu.org> writes:

> cat > foo.el << EOF
> (defsubst foo (a b))
> (foo t)
> EOF
>
> Byte-compile the above file. The Emacs 24.1 byte compiler does not
> complain that the inline function foo is called with too few arguments.

I can confirm that this bug is still present in Emacs 27, but it's weird
that this hasn't come up more often.  I mean, defsubsts are commonly
used, and not having byte compilation warnings about the wrong number of
arguments is something you'd expect to come up more often.

> Emacs 23.1 complains
>
>   foo.el:2:1:Warning: attempt to open-code `anonymous lambda' with
>     too few arguments
>
> till it aborts with
>
>   foo.el:2:1:Error: Variable binding depth exceeds max-specpdl-size
>
> which I do not find very appropriate either.

Nope.

I tried briefly to follow the logic in the stuff that'd give a "attempt
to open-code", but it doesn't seem to be triggered at all in this case.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-08-16 22:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29  2:14 bug#12299: 24.1; no byte compiler warning for inline function call with too few arguments Roland Winkler
2019-08-16 22:46 ` Lars Ingebrigtsen [this message]
2021-07-15 20:29 ` Lars Ingebrigtsen
2021-07-16 15:39   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-17 14:04     ` Lars Ingebrigtsen
2021-07-22 13:14 ` bug#12299: 24.1; no byte compiler warning for inline function call with too few arguments [PATCH] Mattias Engdegård
2021-07-23 11:09   ` Lars Ingebrigtsen
2021-07-23 13:18     ` Mattias Engdegård
2021-12-06 23:36       ` bug#12299: 24.1; no byte compiler warning for inline function call with too few arguments Stefan Kangas
2021-07-23 15:02   ` bug#12299: 24.1; no byte compiler warning for inline function call with too few arguments [PATCH] Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-23 15:52     ` Mattias Engdegård
2021-07-23 16:21       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=8736i0ohib.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=12299@debbugs.gnu.org \
    --cc=winkler@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).