Hi!
> We're talking about a deprecation, not removal of a feature.
There's no point of deprecating if the goal isn't to remove.
> First of all, it doesn't remove the feature, which means that everything
> keeps working as-is, and second, we already have a way to configure error
> reporting for deprecations ("configuration") ;-)
Configuration removes deprecation messages as a whole class, which is
usually not what you want.
> The point of deprecations is precisely to give downstream time to adjust
> and release the adapted code, which we do all the time anyway.
In this case, this would mean "edit every file (that uses standard PHP
functions, which is probably nearly every file in the codebase)", to no
benefit to the user. This is a huge imposition on existing users without
any benefit to them. The fact that they will have time is irrelevant -
they always would have all the time in the world but not upgrading - the
point is that this change is bad for them.
--
Stas Malyshev
smalys...@gmail.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
