From: Andreas Schwab <schwab@linux-m68k.org>
To: 48479@debbugs.gnu.org
Cc: mattiase@acm.org, larsi@gnus.org, rms@gnu.org, monnier@iro.umontreal.ca
Subject: bug#48479: 28.0.50; Crash on `read--expression'
Date: Tue, 18 May 2021 19:46:28 +0200 [thread overview]
Message-ID: <87tun0aqa3.fsf@igel.home> (raw)
In-Reply-To: <jwvim3gnf6m.fsf-monnier+emacs@gnu.org> (Stefan Monnier via's message of "Tue, 18 May 2021 13:12:17 -0400")
On Mai 18 2021, Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" wrote:
>>> Is there any significant advantage of not detecting syntax errors?
>> I don't think I agree that this is a syntax error.
>> What do others think about this? Lars? Stefan? Richard?
>
> I think the condition handler of `condition-case` should be of the form
> (CONDITIONS . BODY) so I think having nil counts as a syntax error, tho
> it's arguable since nil ≃ (nil . nil)
For some reason, the loop at the top of internal_lisp_condition_case
explicitly allows for a handler to be nil.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-05-18 17:46 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 [this message]
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
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=87tun0aqa3.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=48479@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
/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).