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: Wed, 19 May 2021 22:18:24 +0200 [thread overview]
Message-ID: <880B56A7-CCF6-4C04-94F4-D49353E56973@acm.org> (raw)
In-Reply-To: <871ra2czyk.fsf@gnus.org>
19 maj 2021 kl. 20.58 skrev Lars Ingebrigtsen <larsi@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.
next prev parent reply other threads:[~2021-05-19 20:18 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 [this message]
2021-05-25 5:05 ` Lars Ingebrigtsen
2021-05-25 8:29 ` Mattias Engdegård
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=880B56A7-CCF6-4C04-94F4-D49353E56973@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.