On 2 March 2015 at 14:24, Zeev Suraski <z...@zend.com> wrote: > https://wiki.php.net/rfc/array-to-string (which I voted yes to) deviates > from our guidelines of deprecating features first, and removing them > later; > > Should we not go through this deprecation cycle, even if may feel anxious > to get rid of this behavior?
I don't think it's required. The purpose of deprecation notices is to allow people to detect issues in their code that is currently working as they want, and without giving any warning messages. This allows them to estimate how much effort it would be to upgrade to a newer version of PHP, one in which the behaviour is no longer allowed, without actually having to refactor all the code to find out. In this case, the code already produces a notice that says the behaviour is not completely ok, so people are able to detect where array to string conversion is happening. Having an intermediate step of E_DEPRECATED notice would not affect the amount of code that they would need to change nor will it make it significantly easier to detect places in their code where this behaviour is occurring. cheers Dan -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
