Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75501
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.172 as permitted sender)
References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me> <alpine.DEB.2.10.1407141536380.4247@whisky.home.derickrethans.nl>
 <AF61F548-FADC-428F-B76F-1BB82C645D2C@ajf.me> <alpine.DEB.2.10.1407141552290.4247@whisky.home.derickrethans.nl>
 <53C3F70A.7010706@gmail.com> <3aa29e080d70c843713e19a952dfbad6@mail.gmail.com>
 <A1902C97-2854-44C8-AA76-2551DF3F05E5@ajf.me> <3b06c592b0b88bb95d3ae7ea7a93d86f@mail.gmail.com>
 <6AF150D1-1398-43CA-977A-3CF3D51719F4@ajf.me> <5b53012f7b5437d85cdf9972194aa34f@mail.gmail.com>
 <53C408EC.7080104@gmail.com> <5f491f470e902489f036102ae0f437f8@mail.gmail.com>
 <53C41244.5010505@gmail.com>
In-Reply-To: <53C41244.5010505@gmail.com>
MIME-Version: 1.0
Thread-Index: AQJuUFVOlGiX172RfpkkW7aXwqSXwwHleMkPAd/qfJcBzHP03AGqtGtJAmKS0moBHXfO1gIOC4puAaFwLqQB3IH0cgJS+6QEAQ6G0gACRy0FgZmy681Q
Date: Mon, 14 Jul 2014 20:52:34 +0300
Message-ID: <8177fae7c5a1a21ab2bc2b98d7e29d17@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: RE: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening)
From: zeev@zend.com (Zeev Suraski)

> -----Original Message-----
> From: Rowan Collins [mailto:rowan.collins@gmail.com]
> Sent: Monday, July 14, 2014 8:24 PM
> To: internals@lists.php.net
> Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening)
>
> Zeev Suraski wrote (on 14/07/2014):
> > I'd say absolutely yes, if they're PHP developers that's exactly what
> > they'd expect.  After all, if you use 'hello' today in any integer
> > context in PHP, explicit or implicit, that's exactly how it will
> > behavior across the language.
>
> And yet if you use it as a parameter to a type hinted function, it will
> produce
> an error.

Type hints were first and foremost introduced for object oriented safety, as
a part of the major OO model shift Andi and I pushed for in PHP 5.0.  What
you may be alluding to - type hints for arrays and objects - were added at
later time and introduced that small inconsistency you're talking about.
Still, type juggling for scalars has been the fundamental nature of PHP
since the get go;  Type jugging for arrays/objects was always more of an
edge case and perhaps even a misfeature.

> You can be consistent with casts, or consistent with existing type hints,
> but not
> both.

Type looseness defines PHP.  Type hints do not.

Zeev