RE: [PHP-DEV] Coercive Scalar Type Hints RFC
| From: | Pierre Joye | Date: | Mon, 23 Feb 2015 18:51:53 +0000 |
| Subject: | RE: [PHP-DEV] Coercive Scalar Type Hints RFC | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-83599@lists.php.net to get a copy of this message | ||
On Feb 23, 2015 10:09 AM, "Zeev Suraski" <zeev@zend.com> wrote:
> > I agree if we can avoid an INI setting, but this will surely lead to a
> > Python 2/3
> > situation.
>
> I don't think it will. But instead of guessing, we should try the patch
> with some real world apps and find out. I think that if we find out we
can
> migrate Drupal (or whatever) in a couple of days or even a couple of weeks
> to be E_DEPRECATED free - this approach is very viable. If it requires
> months and months of updates, it'll be a different story.
I have to disagree with this point. Changing the casting rule is not
something that can be easily "fixed".
It is why i like the dual mode choices. There is nothing to port (except
the few things we had to break already), unless one app explicitly wants to
move to strict internally, partially or totally (don't see why one would do
that).
Cheers,
Pierre