From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Mattias Engdegård" <mattiase@acm.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 07:05:56 +0200 [thread overview]
Message-ID: <87r1hvqu6j.fsf@gnus.org> (raw)
In-Reply-To: <8635ulvbbx.fsf@protected.rcdrun.com>
Mattias Engdegård <mattiase@acm.org> writes:
> 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?
Not really -- it's just not explicitly stated that the empty version is
allowed, but I guess it can be reasonably inferred (and that the return
value of emptiness is nil).
>> (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.
On
(condition-case nil
(foo)
())
? A warning is nice, but I think signalling an error would be
excessive.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-25 5:05 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 [this message]
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
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=87r1hvqu6j.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=48479@debbugs.gnu.org \
--cc=mattiase@acm.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).