From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Saving match data
Date: Wed, 28 Sep 2016 18:49:37 +0200 [thread overview]
Message-ID: <87twd0j7fi.fsf@web.de> (raw)
In-Reply-To: <jwvlgyc9fof.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Wed, 28 Sep 2016 12:11:00 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> That would imply adding save-match-data *everywhere*. It's an enormous
> amount of work, can't be automated, and comes with only two obvious
> results:
> - our Elisp source code will be significantly larger.
> - Emacs will be slower.
This sounds crazy. Sorry about this ignorant question: Why do we use
this model of match data: a global state that is changed as a side
effect in thousands of circumstances. If you really need the match
data, the common way is to suppress that it is changed. This discussion
shows that this approach seems to have great downsides, and it doesn't
seem very "lispy" anyway.
Why don't we just let the programmer explicitly save the match data
(e.g. to a symbol) when he is interested in it (FWIW this is already
possible with `match-data' and `save-match-data'). That would be more
transparent and work around this kind of problem.
Michael.
next prev parent reply other threads:[~2016-09-28 16:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 14:01 Saving match data Philipp Stephani
2016-09-28 15:03 ` Eli Zaretskii
2016-09-28 16:11 ` Stefan Monnier
2016-09-28 16:49 ` Michael Heerdegen [this message]
2016-09-28 18:25 ` Stefan Monnier
2016-09-28 18:37 ` Michael Heerdegen
2016-09-28 20:00 ` Eli Zaretskii
2016-09-28 20:15 ` Michael Heerdegen
2016-09-28 20:22 ` Eli Zaretskii
2016-09-28 20:42 ` Michael Heerdegen
2016-09-28 20:58 ` Lars Ingebrigtsen
2016-09-29 2:36 ` Eli Zaretskii
2016-10-08 4:02 ` Michael Heerdegen
2016-10-08 6:25 ` Eli Zaretskii
2016-10-08 15:06 ` Stefan Monnier
2017-06-16 19:24 ` Philipp Stephani
2017-06-16 19:53 ` Stefan Monnier
2017-06-16 22:16 ` Philipp Stephani
2017-06-17 13:53 ` Stefan Monnier
2017-06-17 14:02 ` Philipp Stephani
2017-10-08 15:56 ` Philipp Stephani
2017-10-08 16:01 ` Philipp Stephani
2016-09-28 17:00 ` Marcin Borkowski
2016-09-29 9:29 ` Uwe Brauer
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=87twd0j7fi.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@gnu.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).