Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95438
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain mudsite.com designates 209.85.217.176 as permitted sender)
MIME-Version: 1.0
References: <CAC0n1EC8=+gnbqn+R_Z8YFVi=XGT4d+FGk2NU+6_Tsv1-O8+eg@mail.gmail.com>
 <CAEZPtU431Sa_uRn26xA3GwUk4U0o-k4FXgRbxVtMjHWY4c8NNw@mail.gmail.com>
 <CAEZPtU5Cw71Ta9eWmsYG6u4OPtPY0yCOGESyDw97WG6QOWgOOQ@mail.gmail.com>
 <CAEZPtU7VkTJaJOg1LBCoQkOTc1YXHpOuTKouGtXxuBg-oyiR7g@mail.gmail.com>
 <CAC0n1ECcnokyvV+m115nHtttqx-YBNb8biQ1eFaoubZrw060VQ@mail.gmail.com> <c0afd0b0-b700-f639-96e5-e47566d44fb6@gmail.com>
In-Reply-To: <c0afd0b0-b700-f639-96e5-e47566d44fb6@gmail.com>
Date: Wed, 24 Aug 2016 22:48:20 +0000
Message-ID: <CADVQu1Sj0gJygwkETTOAN0CKnFqKvJrO6n2hEtH-yBo_uBmv7Q@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>, Rodrigue Villetard <rodrigue.villetard@gmail.com>, 
	Pierre Joye <pierre.php@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c12400690c7a4053ad91483
Subject: Re: [PHP-DEV] Write down a deprecation policy
From: dave+php@mudsite.com (David Walker)

--94eb2c12400690c7a4053ad91483
Content-Type: text/plain; charset=UTF-8

On Wed, Aug 24, 2016 at 3:46 PM Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> Hi!
>
> >   * Explicit remaining time to live of a deprecated feature (ie. in
> > which future version of php this deprecated functionality will be
> > dropped)
>
> I don't think we should be in a rush to drop deprecated things. Java,
> for example, deprecates a lot of things but drops them very rarely. And
> I think it's one of the things they got right - deprecation tells you we
> don't recommend using it, but if you still need it for some reason we
> didn't think of - we won't block you.
>

+1

I wouldn't want to enforce a deprecated functionality _must_ be removed in
the next {insert duration here}.  What I would rather it read would be,
when a core change would otherwise break the deprecated functionality it
would be removed.  Deprecated should just flag some functionality as: will
be removed in the event something would render the functionality moot.  I
would, however, encourage when functionality is deprecated it be well
documented how to convert to the recommended functionality.

--
Dave

--94eb2c12400690c7a4053ad91483--