Den 2021-03-22 kl. 15:58, skrev Ben Ramsey:
On Mar 22, 2021, at 04:24, Nikita Popov <nikita....@gmail.com> wrote:
Hi internals,
It's time for another deprecation RFC:
https://wiki.php.net/rfc/deprecations_php_8_1
This is a collection of minor deprecations that various people have put
together over the last ~2 years. This RFC was formerly targeted at PHP 8.0,
but was delayed to PHP 8.1 to reduce the amount of changes necessary for
PHP 8.0 compatibility.
As usual, each deprecation will be voted in isolation.
As we're still early in the release cycle, it's still possible to add
additional deprecation candidates, given reasoning for the deprecation, as
well as available alternatives.
Of course, if there are compelling technical reasons why something should
not be deprecated, we can move things into the "Removed from this proposal"
section, in which case it will serve as documentation why some
functionality should not deprecated.
Given Rowan’s thread [1] on `utf8_encode()` and `utf8_decode()`, should we
consider adding these functions to this list or mentioning them in this
RFC as being handled separately?
Cheers,
Ben
[1] https://externals.io/message/113645
In order for that I think a clearer / better motivation is needed.
For instance bug reports or community / documented feedback that these
functions are giving rise to problems / are misused.
Maybe also a checking how frequently thay are used in different Open
source libraries. Found several occurences in the Revive ad server.
r//Björn L
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
