Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75582
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.178 as permitted sender)
References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me> <16D48604-0C0A-4613-91A4-21392E3A2636@ajf.me>
 <CAGAGxbZG+c46P4E2pmEHNnEv=4DyTrHOuXbZu3zAOSU3M6-A-A@mail.gmail.com>
 <05CE2216-C5D9-4937-9F2E-AA1407284D9F@ajf.me> <53C460DF.5040304@sugarcrm.com>
 <53C53A96.2040303@gmail.com> <53C55342.1010207@sugarcrm.com>
 <53C563B3.6060905@gmail.com> <CAPhkiZwvqW=d3Ayn-=Hx5HfkcOFB+gQ6rRoFThxA8hESK4WLrA@mail.gmail.com>
 <54536191-1B92-4933-973F-0C8289D13A4C@ajf.me>
In-Reply-To: <54536191-1B92-4933-973F-0C8289D13A4C@ajf.me>
MIME-Version: 1.0
Thread-Index: AQJuUFVOlGiX172RfpkkW7aXwqSXwwLGIEDMAn0sGnoDLh5SUQGHGGlvAc6JkJwCOz0MXAIckqSUAcstGVQBlZLKH5nJEiBA
Date: Wed, 16 Jul 2014 12:29:13 +0300
Message-ID: <00d12255efc53466245b21a83ff7d474@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>, Andrey Andreev <narf@devilix.net>
Cc: Rowan Collins <rowan.collins@gmail.com>, Stas Malyshev <smalyshev@sugarcrm.com>, 
	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: Andrea Faulds [mailto:ajf@ajf.me]
> Sent: Tuesday, July 15, 2014 10:48 PM
> To: Andrey Andreev
> Cc: Rowan Collins; Stas Malyshev; internals@lists.php.net
> Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening)
>
>
> On 15 Jul 2014, at 20:43, Andrey Andreev <narf@devilix.net> wrote:
>
> > I'm sorry, I know what you mean here and I'm not criticizing you
> > specifically (in fact, I'm intentionally taking it ouf of context),
> > but that's "PHP internals", not "PHP community".
> >
> > The PHP community that I know, wants to have _both_ type cast hinting
> > and strict type declarations.
>
> I'm not sure that's quite the case. There are camps wanting one, there
are
> camps wanting the other, I suppose some want both, but to me that seems
like
> a not-a-compromise compromise solution. The point of this RFC, to some
> extent, is to be a reasonable compromise between completely strict
> declarations and cast hinting, providing the safety of the first and the
flexibility
> of the second. I think it strikes the balance well.

For me the introduction of a new set of rules is a deal breaker.
I'm -1 on the RFC the way it is, and +1 if we implement these 'hints' as
implicit casts, plus change implicit casts to emit E_CAST in case of loss
of data or 'bogus' conversions.

Why insist E_RECOVERABLE_ERROR and introduce this effectively new set of
rules, instead of switching to E_CAST and maintain consistency?
Maintaining consistency is a HUGE deal.  Every such feature we add that
you need to learn more rules/exceptions for make PHP harder to learn.

Zeev