unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Ulrich Mueller <ulm@gentoo.org>, Eli Zaretskii <eliz@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	73596@debbugs.gnu.org
Subject: bug#73596: 29.4; empty (let) does not signal an error
Date: Sat, 12 Oct 2024 17:40:30 +0200	[thread overview]
Message-ID: <u4j5hxrbl@gentoo.org> (raw)
In-Reply-To: <87ldyts8po.fsf@igel.home> (Andreas Schwab's message of "Sat, 12 Oct 2024 16:21:23 +0200")

>>>>> On Sat, 12 Oct 2024, Andreas Schwab wrote:

> On Okt 12 2024, Ulrich Mueller wrote:
>> (func-arity 'let)  ⇒  (1 . unevalled)
>> 
>> Shouldn't this be updated to return (0 . unevalled) when empty (let)
>> is allowed?

> $ emacs -batch -eval '(let)'

> Error: wrong-number-of-arguments (let 0)
>   (let)
>   eval((let) t)
>   command-line-1(("-eval" "(let)"))
>   command-line()
>   normal-top-level()
> Wrong number of arguments: let, 0

That's even stranger then, because it seems to depend on how Emacs
is invoked:

$ echo "(princ (let))" >foo.el
$ emacs -Q -batch -L . -l foo.el
nil

$ emacs -Q
M-: (let) RET
⇒ nil





  reply	other threads:[~2024-10-12 15:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 12:54 bug#73596: 29.4; empty (let) does not signal an error Ulrich Mueller
2024-10-12 11:26 ` Eli Zaretskii
2024-10-12 13:43   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-12 13:54     ` Ulrich Mueller
2024-10-12 14:21       ` Andreas Schwab
2024-10-12 15:40         ` Ulrich Mueller [this message]
2024-10-12 15:51           ` Andreas Schwab
2024-10-12 15:57             ` Ulrich Mueller
2024-10-12 16:32               ` Andreas Schwab
2024-10-13  5:04                 ` Michael Heerdegen 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=u4j5hxrbl@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=73596@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=schwab@linux-m68k.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).