I think I was not clear. *Every* 'break' I report here won't generate anything more than E_DEPRECATED in the final implementation. By definition. Ne need to wait for a better patch.
François > -----Message d'origine----- > De : [email protected] [mailto:[email protected]] De la part de Yasuo > Ohgaki > Envoyé : mardi 24 février 2015 06:09 > À : francois > Cc : Pierre Joye; Zeev Suraski; Anthony Ferrara; PHP internals > Objet : Re: [PHP-DEV] Coercive Scalar Type Hints RFC - BC breaks > > Hi Francois, > > On Tue, Feb 24, 2015 at 2:01 PM, François Laupretre <[email protected]> > wrote: > > > I don’t understand which E_DEPRECATED you’re talking about. The > > E_DEPRECATED mechanism proposed in the RFC is not implemented yet. > But, > > yes, all these failures will raise E_DEPRECATED, as none of them appears in > > PHP 5. In such a case, hiding E_DEPRECATED will remove every failure. > > > OK. I missed current patch status. Then it seems to early for testing. > I think we need result w/o E_DEPRECATED errors. > I suggest to wait a little more. > > Regards, > > -- > Yasuo Ohgaki > [email protected] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
