GNU bug report logs - #48479
28.0.50; Crash on `read--expression'

Previous Next

Package: emacs;

Reported by: Jean Louis <bug <at> gnu.support>

Date: Mon, 17 May 2021 14:39:02 UTC

Severity: normal

Tags: fixed

Found in version 28.0.50

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Mattias Engdegård <mattiase <at> acm.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 48479 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: bug#48479: 28.0.50; Crash on `read--expression'
Date: Wed, 19 May 2021 22:18:24 +0200

19 maj 2021 kl. 20.58 skrev Lars Ingebrigtsen <larsi <at> gnus.org>:

> I was thinking of the
> 
> (condition-case nil
>    (foo)
>  (error))
> 
> case...  (I.e., with a missing handler body.)  I'm not sure whether
> that's supposed to or not.

Thank you, and yes, that is valid; a body can be empty (it's an implicit progn).
I don't think an empty body in an error handler warrants a warning more than anywhere else. Do you?

> (condition-case nil
>    (foo))
> 
> doesn't give a warning.

Right, but its meaning is also well-defined and could even be useful in a macro. I'm slightly more inclined to accept a warning here, but we are drifting away from the original question: for syntactically invalid handlers, like (), can we signal an error? I think we can.
This bug report was last modified 4 years and 81 days ago.

Previous Next

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