GNU bug report logs - #73596
29.4; empty (let) does not signal an error

Previous Next

Full log

Message #26 received at 73596 <at> debbugs.gnu.org (full text, mbox):

From: Ulrich Mueller <ulm <at> gentoo.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: Ulrich Mueller <ulm <at> gentoo.org>, Eli Zaretskii <eliz <at> gnu.org>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>, 73596 <at> debbugs.gnu.org
Subject: Re: bug#73596: 29.4; empty (let) does not signal an error
Date: Sat, 12 Oct 2024 17:40:30 +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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.