The RFC is now updated to state that changing E_DEPRECATED to fatal error cannot in any way happen before a delay of 5 years, starting with first stable PHP distribution containing the STH feature.
> -----Message d'origine----- > De : François Laupretre [mailto:franc...@php.net] > Envoyé : vendredi 27 février 2015 02:41 > À : 'Anthony Ferrara'; 'Zeev Suraski' > Cc : internals@lists.php.net > Objet : RE: [PHP-DEV] A different user perspective on scalar type > declarations > > > De : Anthony Ferrara [mailto:ircmax...@gmail.com] > > > They run without triggering E_DEPRECATED errors? Because that means > > they will break with 8 (which by your own words is closer to 2-3 years > > out than 9-10). > > Absolutely no date is planned to switch E_DEPRECATED to > E_RECOVERABLE_ERROR. It must be clear for everyone that we don't have to > hurry there. My personal opinion is that it cannot be before at least 5 years, > and maybe more. If I had to announce a major version, I would say 9, not 8. > And no decision will be made before we have a large consensus about it. > Once again, there will be no good reason to hurry for it. > > Zeev, can't we put a sentence in the RFC where we state that the > E_DEPRECATED stage cannot be turned off before, say, 5 years at least ? > Once the statement is voted with the RFC, users are protected. > > Regards > > François > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
