On Mar 20, 2015 12:14 AM, "François Laupretre" <franc...@php.net> wrote: > > > De : Zeev Suraski [mailto:z...@zend.com] > > > > 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; It’s addressed in the RFC – but I’m a bit worried that this opens > > the door to jumping from any sort of notice/warning into errors or removed > > features without any deprecation phase. > > > > In comparison, in Nikita’s RFC for removing E_STRICT – there aren’t any > > proposed ‘jumps’ to E_RECOVERABLE_ERROR that don’t first go through > > E_DEPRECATED. > > > > Should we not go through this deprecation cycle, even if may feel anxious > > to get rid of this behavior? > > Sorry for the delay but I could not send emails during the last 3 weeks. > > As you may have noticed if you had a look at the RFC or twitter, I have decided to follow people's suggestion. Array to string conversion will raise E_DEPRECATED in 7.0, and, then, fatal error in 7.1 or 7.2.
Hmm.. Sorry but no. I really do not think we can do this, this will bring a major BC in 7.1+ and we do not allow BC but in extreme cases. > Please note that the switch from E_DEPRECATED to fatal error won't require any new RFC/discussion/vote as the fatal error is considered as approved. I just introduce an E_DEPRECATED phase for 7.0. Well, if it is, do it in 7.0. But changing that all of a sudden and making it fatal in 7.1+ is an extremely bad idea :) > Regards > > François > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >
