Re: Confused by y-or-n-p

[Eli Zaretskii]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: larsi@gnus.org,  stefankangas@gmail.com,  rms@gnu.org,  juri@linkov.net,
>   rudalics@gmx.at,  emacs-devel@gnu.org,  drew.adams@oracle.com
> Date: Mon, 04 Jan 2021 13:02:15 -0500
> 
> I was thinking of changing `make-obsolete` and friends so they
> undefine (or refrain from defining) the function/variable.  They could
> do so by testing `emacs-version` (or some other way to detect the
> `master` code) along with some extra config vars (e.g. a var to force
> the behavior globally on way or the other or only for some
> functions/variables).

That's fine, but then such a mechanism can handle only a small portion
of the changes that can be perceived as incompatible with past
behavior.  For example, the change which started this thread cannot be
easily handled that way, because it is not about making something
obsolete.

Most of the changes we are talking about don't obsolete anything.

We should also consider the effects of this on code readability.  It
is unexpected to have make-obsolete undefine its subject, let alone do
it or not depending on some under-the-hood magic.