bug#13260: 24.3.50; save match data for core functions like `delete-char' and `delete-backward-char'?

[Stefan Monnier]

>>> I know the policy is to let any function assume the match data
>>> are not saved, but I think an exception would be useful here.
>> Why?
> Because delete-char is very low-level and because it is hard to
> guess why it would modify the match data -- hence very easy to
> assume it will not, while it does.

AFAIK delete-char does not modify the match-data any more than other
buffer-modifying operations (such as delete-region, insert, ...).
They all just modify the buffer, which is turn can modify the match-data
because it runs various hooks which can do all kinds of things.

> Principle of least surprise?

The rule "expect the match-data to be destroyed all the time" is the one
that leads to the least surprise.  99% of the functions can destroy the
match-data, even though they may preserve it in 99% of
the circumstances.

And in 99% of the cases where they do destroy the match-data, nobody
cares anyway, which is why we shouldn't always save-match-data.


        Stefan