unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattiase@acm.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48479@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#48479: 28.0.50; Crash on `read--expression'
Date: Tue, 25 May 2021 10:29:18 +0200	[thread overview]
Message-ID: <BD5F39EC-2D3D-46DA-B46D-FC9F7DE0FD31@acm.org> (raw)
In-Reply-To: <87r1hvqu6j.fsf@gnus.org>

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?






      reply	other threads:[~2021-05-25  8:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 11:39 bug#48479: 28.0.50; Crash on `read--expression' Jean Louis
2021-05-17 15:14 ` Eli Zaretskii
2021-05-17 20:01   ` Mattias Engdegård
2021-05-18 11:29     ` Eli Zaretskii
2021-05-18 15:00       ` Mattias Engdegård
2021-05-18 15:09         ` Eli Zaretskii
2021-05-18 15:42           ` Mattias Engdegård
2021-05-18 16:45             ` Eli Zaretskii
2021-05-18 17:12               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-18 17:46                 ` Andreas Schwab
2021-05-19 16:36                   ` Mattias Engdegård
2021-05-19 14:53                 ` Lars Ingebrigtsen
2021-05-19 15:13                   ` Eli Zaretskii
2021-05-19 16:33                   ` Mattias Engdegård
2021-05-19 18:58                     ` Lars Ingebrigtsen
2021-05-19 20:18                       ` Mattias Engdegård
2021-05-25  5:05                         ` Lars Ingebrigtsen
2021-05-25  8:29                           ` Mattias Engdegård [this message]

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=BD5F39EC-2D3D-46DA-B46D-FC9F7DE0FD31@acm.org \
    --to=mattiase@acm.org \
    --cc=48479@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).