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: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Mattias Engdegård <mattiase <at> acm.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 20:58:59 +0200

Mattias Engdegård <mattiase <at> acm.org> writes:

> 19 maj 2021 kl. 16.53 skrev Lars Ingebrigtsen <larsi <at> gnus.org>:
>
>> I thought we did warn about this, but some testing now seems to indicate
>> that we don't?
>
>  (condition-case nil t nil)
>
> definitely elicits a warning by the byte-compiler (not about the
> syntax per se but about `nil` not being a condition). Or were you
> thinking about something else?

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.  A handler is defined as

(CONDITIONS BODY...)

but a BODY in many other circumstances are allowed to be missing.

Also note that

(condition-case nil
    (foo))

doesn't give a warning.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no
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.