Re: [RFC] Deprecations for 7.4
| From: | Claude Pache | Date: | Fri, 21 Jun 2019 17:54:06 +0000 |
| Subject: | Re: [RFC] Deprecations for 7.4 | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-106016@lists.php.net to get a copy of this message | ||
> Le 21 juin 2019 à 17:20, Kalle Sommer Nielsen <kalle@php.net> a écrit :
>
> Greetings Internals
>
> Nikita and I would like to open the discussion for the RFC:
> "Deprecations for 7.4", this RFC targets a larger set of various
> features targeting for deprecation in 7.4 with the intention of
> removal in PHP 8.0.
>
> https://wiki.php.net/rfc/deprecations_php_7_4
>
> If there is no major objections to this RFC, then voting will begin in
> a 2 weeks time.
>
> Regards,
> Nikita & Kalle
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
I object to the following deprecations:
------------
apache_request_headers().
The function has that name because once upon a time it was available only when PHP run as an Apache
module. But although it (and its irregularly-named alias
getallheaders()) is now
available somewhere else, the functionality has not changed for those that run PHP as an Apache
module.
Also, according to the documentation, another function, apache_response_headers(), is
also available to other SAPIs. However, it has the benefit of not having a documented alias, so that
it can escape the deprecation proposal?
Note also the existence of nsapi_request_headers() function that (according to the
documentation) does the same thing than getallheaders() when PHP runs as a NSAPI
module.
And last but not least, *_request_headers()is more precisely named than
getallheaders() (given the existence of *_response_header() functions).
------------
is_writeable().
That “writeable” is “a spelling mistake” (as opposed to an “uncommon alternative
spelling”) is an opinion that is not really proveable.
------------
—Claude