Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75473
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.200 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <0C5F203F-3DA7-4C38-A132-955836AF2274@ajf.me>
Date: Mon, 14 Jul 2014 16:20:33 +0100
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <9714BF6C-2A1E-49B7-AEA8-CB384870FC08@ajf.me>
References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me> <16D48604-0C0A-4613-91A4-21392E3A2636@ajf.me> <53C3E31C.1070306@gmail.com> <0C5F203F-3DA7-4C38-A132-955836AF2274@ajf.me>
To: Rowan Collins <rowan.collins@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening)
From: ajf@ajf.me (Andrea Faulds)


On 14 Jul 2014, at 15:17, Andrea Faulds <ajf@ajf.me> wrote:

>=20
> On 14 Jul 2014, at 15:03, Rowan Collins <rowan.collins@gmail.com> =
wrote:
>=20
>> Looking at the current table in the RFC, I'm not clear why NULL =
should pass as any value, but not array. Could it not behave the same as =
the existing type hints, i.e. accepted only if declared as a default?
>>=20
>> function foo(array $bar) { } foo(null); // ERROR
>> function foo(array $bar=3Dnull) { } foo(null); // OK, $bar =3D=3D =
NULL
>> function foo(int $bar) { } foo(null); // ERROR
>> function foo(int $bar=3Dnull) { } foo(null); // OK, $bar =3D=3D NULL
>=20
> I=92m thinking this as well. I wonder if perhaps it should be casted =
by default, but if you make it explicitly nullable, it won=92t cast if =
NULL is passed.

This has been done now, as it was what I wanted to do and Anthony=92s =
original intention. It works like this:

    function foo(int $a) { var_dump($a); }
    function bar(int $a =3D NULL) { var_dump($a); }

    foo(NULL); // int(0)
    bar(NULL); // NULL

--
Andrea Faulds
http://ajf.me/