From: Philipp <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Pip Cet <pipcet@gmail.com>, 33414@debbugs.gnu.org
Subject: bug#33414: 27.0.50; inhibit-changing-match-data can be t in syntax-propertize functions, breaking backtrace and looking-at
Date: Sat, 4 Sep 2021 20:39:46 +0200 [thread overview]
Message-ID: <22C40A08-9611-4925-B840-8F3795175B0F@gmail.com> (raw)
In-Reply-To: <87r1eylsea.fsf@gnus.org>
> Am 12.08.2021 um 15:11 schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
>
> `inhibit-changing-match-data' just seems like a bad interface to me.
Yes, using a public dynamic variable (i.e., public global mutable state) to influence the behavior of a function is normally a bad idea. Effectively, the dynamic variable becomes a hidden parameter to the function, and robust code has to bind it explicitly do override any surprising binding up the call stack. You normally don't see such a coding style in other programming languages, and ELisp would be better off without it, too.
next prev parent reply other threads:[~2021-09-04 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 13:30 bug#33414: 27.0.50; inhibit-changing-match-data can be t in syntax-propertize functions, breaking backtrace and looking-at Pip Cet
2018-11-17 13:46 ` Eli Zaretskii
2018-11-17 14:14 ` Pip Cet
2018-11-17 14:36 ` Eli Zaretskii
2021-08-12 13:11 ` Lars Ingebrigtsen
2021-09-04 18:39 ` Philipp [this message]
2021-09-04 19:33 ` bug#33414: [External] : " Drew Adams
2021-09-05 9:29 ` Lars Ingebrigtsen
2021-09-05 9:40 ` Eli Zaretskii
2021-09-05 9:45 ` Lars Ingebrigtsen
2021-09-05 9:55 ` Eli Zaretskii
2021-10-07 18:49 ` Lars Ingebrigtsen
2021-10-07 19:07 ` bug#33414: [External] : " Drew Adams
2021-10-07 19:11 ` Lars Ingebrigtsen
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=22C40A08-9611-4925-B840-8F3795175B0F@gmail.com \
--to=p.stephani2@gmail.com \
--cc=33414@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=pipcet@gmail.com \
/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).