Re: [RFC] Deprecations for PHP 7.2
| From: | Derick Rethans | Date: | Sun, 20 Nov 2016 22:42:28 +0000 |
| Subject: | Re: [RFC] Deprecations for PHP 7.2 | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-97095@lists.php.net to get a copy of this message | ||
On Fri, 18 Nov 2016, Nikita Popov wrote:
> Hi internals!
>
> I've submitted this RFC for PHP 7.1 previously, but didn't follow through
> due to time constraints. Now I'd like to propose an extended version for
> PHP 7.2 and vote on it sooner rather than later to avoid a repeat
> performance.
>
> https://wiki.php.net/rfc/deprecations_php_7_2
>
> The RFC combines a number of deprecation and removal proposals. Each one
> will get a separate 2/3 majority vote. The RFC overlaps with some recently
> discussed topics (each, binary strings) -- I'm fine with dropping these if
> someone has a more specific RFC.
I wouldn't deprecate things that 1. have no replacement, 2. are very
much in use, or 3. are harmless.
__autoload is one of group (2). I think this is used a lot, and would
*not* want to deprecate this until PHP 8.
I also do not see why (binary) should be removed, as it fits in category
3.
In general, I think you should have a good reason *why* to remove them,
and just "it's not what we suggest you use" is not good enough. It
should be a general *bad* thing, before it should be considered for
removal.
Right now, the only thing I can think of is removing
mbstring.func_overload.
For ini settings, you should not throw a deprecation warning if the
setting is set to *off*. This covers mbstring.func_overload , but it
seems you have changed that since I read this RFC for the first time.
cheers,
Derick