Re: when do we remove backward compatibility definitions?

[Eli Zaretskii]

> Cc: address@hidden, address@hidden
> From: Paul Eggert <address@hidden>
> Date: Tue, 21 Nov 2017 12:18:41 -0800
> 
> On 11/21/2017 12:03 PM, Eli Zaretskii wrote:
> > Let's instead solve practical problems with such issues.  Are there
> > any practical problems here?  If so, what are they?
> 
> The practical problem is that when we have cruft in the Emacs source 
> code that makes maintenance harder

No, we don't have any cruft, not from my POV.

> My attempt at writing a guideline for supporting obsolete Emacs features 
> is intended to be along similar lines. It is not meant to be 
> prescriptive and so I shouldn't have used the word "policy" to describe 
> it. It is merely meant as a common-sense guideline for when Emacs 
> features are so obsolete that they can be removed if that simplifies 
> maintenance.

Sorry, I'm not interested in discussing abstract policies that have no
specific problems behind them.  It's a waste of our time.  If there is
a specific problem with the variables Sam saw, let's discuss those
instead.