Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75439
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53C2DC03.2050609@gmail.com>
References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me> <CAF+90c-ojALBgeyXu+f2tW6LoW8+4XGVpu_+i9SyX=u4RSoxug@mail.gmail.com>
 <027E65EF-C4FC-474C-92BB-D99EFADDEEED@ajf.me> <ada4093ad61814c182f8ca31939962ea@mail.gmail.com>
 <BDC11A4E-0610-49A3-B8AE-E9D3627B75C8@ajf.me> <eab1ceea2084415d21736a69c4ac6fdc@mail.gmail.com>
 <53C29EE4.3090808@gmail.com> <63e5b1c38d6e0c5111987e78d9b59be3@mail.gmail.com>
 <E2926DD2-B0AE-4A87-BEA8-F07FE49CE4B5@ajf.me> <b3026b451453e3c2412bbf45c59f5003@mail.gmail.com>
 <53C2AF35.40003@gmail.com> <93bb0c689ccca03a0af46c51abf0e11f@mail.gmail.com>
 <53C2C84A.6060308@garfieldtech.com> <49C63232-AB78-4B2C-A3E4-B21748D5D489@ajf.me>
 <53C2DC03.2050609@gmail.com>
Date: Mon, 14 Jul 2014 13:09:42 +0300
Message-ID: <CAL0xaBHa6uYZjn9K-pYr8=ovygX8mToCxfKxqBhrvVvZCjNTNQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c16606980cad04fe247e8c
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening)
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--001a11c16606980cad04fe247e8c
Content-Type: text/plain; charset=UTF-8

Hello!

As a user land developer I do think that over thinking this is going to end
up in disaster.
We already have quite good implementation for the array and object hints,
they do their job and do it good. No need to change those at all - leave
them as is - no need to add magic with casts and all that. Function/method
requires an array? Make casts explicitly and pass it an array and not an
integer.

Primitive type hints are a little different - they are easily cast into
each other for the most part. The only edge case is when we loose data. In
this case we need a E_STRICT or something like that (I would vote for
E_TYPEHINT_CAST - because you will be able to disable only typehint
warnings/errors without disabling E_STRICT), so we can collect these errors
and fix our code by adding checks/casts/whatever. But this automatic
casting should work only between string, integer, float, bool and null
types and only between these. No automatic casting of these 5 to arrays or
objects.

PHP does not need a type hinting system forces you to first make a
prototype without any type hints because you get catchable errors - you can
handle them, but you can't actually just continue right where the error
occurred. You just need to get a warning, that you can disable via
error_reporting, and just make your prototype with all the type hints you
need and deal with the cast warnings in the type hints later on.

P.S. And on that "var integer $variable" in methods/functions. People, when
you have internal functions returning null|array, bool|array and so on -
this is pointless.

--001a11c16606980cad04fe247e8c--