Re: Write down a deprecation policy
| From: | David Walker | Date: | Wed, 24 Aug 2016 22:48:20 +0000 |
| Subject: | Re: Write down a deprecation policy | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95438@lists.php.net to get a copy of this message | ||
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