[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#48479: 28.0.50; Crash on `read--expression'
From: |
Mattias Engdegård |
Subject: |
bug#48479: 28.0.50; Crash on `read--expression' |
Date: |
Tue, 25 May 2021 10:29:18 +0200 |
Hello Lars,
25 maj 2021 kl. 07.05 skrev Lars Ingebrigtsen <larsi@gnus.org>:
> (condition-case nil
> (foo)
> ())
>
> ? A warning is nice, but I think signalling an error would be
> excessive.
Why is an error excessive for that syntax mistake, when we signal an error for
(condition-case
(do-something)
(error "failure"))
and
(condition-case nil
(do-something)
error "failure")
? Wouldn't the user be best served with an error in all cases?
- bug#48479: 28.0.50; Crash on `read--expression', (continued)
- bug#48479: 28.0.50; Crash on `read--expression', Lars Ingebrigtsen, 2021/05/19
- bug#48479: 28.0.50; Crash on `read--expression', Eli Zaretskii, 2021/05/19
- bug#48479: 28.0.50; Crash on `read--expression', Mattias Engdegård, 2021/05/19
- bug#48479: 28.0.50; Crash on `read--expression', Lars Ingebrigtsen, 2021/05/19
- bug#48479: 28.0.50; Crash on `read--expression', Mattias Engdegård, 2021/05/19
- bug#48479: 28.0.50; Crash on `read--expression', Lars Ingebrigtsen, 2021/05/25
- bug#48479: 28.0.50; Crash on `read--expression',
Mattias Engdegård <=