From: "Mattias Engdegård" <mattiase@acm.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48479@debbugs.gnu.org
Subject: bug#48479: 28.0.50; Crash on `read--expression'
Date: Tue, 18 May 2021 17:00:33 +0200 [thread overview]
Message-ID: <7D502665-A194-477F-89EF-89E617AA1109@acm.org> (raw)
In-Reply-To: <83r1i4s2kd.fsf@gnu.org>
18 maj 2021 kl. 13.29 skrev Eli Zaretskii <eliz@gnu.org>:
> What would be the advantage of making it an error?
Detecting mistakes, early. There are many possible reasons for making ones; misplaced brackets is but one.
In the Lisp implementation tradition we do not benefit from a monolithic parser that verifies all aspects of the grammar in one go, so extra care has to be taken in each special form. A sloppy parse is unhelpful: it hides mistakes and impedes backward-compatible language evolution. There is no advantage to it.
Furthermore, reporting syntax errors as warnings but still accepting the code really makes no sense, other as a temporary measure to avoid breaking invalid code right away (if that is seen as something positive).
next prev parent reply other threads:[~2021-05-18 15:00 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 [this message]
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
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=7D502665-A194-477F-89EF-89E617AA1109@acm.org \
--to=mattiase@acm.org \
--cc=48479@debbugs.gnu.org \
--cc=eliz@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).