Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98344
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.66 as permitted sender)
Date: Thu, 23 Feb 2017 08:58:04 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <CAPhkiZwf3sWY3d8ZVmFcMmAGcEgHE9pQiZDks=YxGDDVEYdeKg@mail.gmail.com>
References: <C6.E7.11648.B000EA85@pb1.pair.com> <CAPhkiZwf3sWY3d8ZVmFcMmAGcEgHE9pQiZDks=YxGDDVEYdeKg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net,Andrey Andreev <narf@devilix.net>,=?UTF-8?Q?Micha=C5=82?= <aaatoja@o2.pl>
CC: "internals@lists.php.net" <internals@lists.php.net>
Message-ID: <E416AFA2-CF86-4C40-92EF-7731943250B1@gmail.com>
Subject: Re: [PHP-DEV] Nullable types and strict type-hinting with default null value
From: rowan.collins@gmail.com (Rowan Collins)

On 23 February 2017 07:23:02 GMT+00:00, Andrey Andreev <narf@devilix=2Enet>=
 wrote:
>Hi,
>
>On Wed, Feb 22, 2017 at 11:18 PM, Micha=C5=82 <aaatoja@o2=2Epl> wrote:
>
>> "The
>declaration
>> can be made to accept NULL values if the default value of the
>parameter is
>> set to NULL"=2E
>
>This isn't just a PHP 7 work-around for null types, it has existed
>since
>object type hints were introduced and is very widespread=2E

Indeed, it's far too early to think about forcing people to change all the=
ir code to the ? notation=2E I'm also not convinced of the value even once =
that's established; it's not like "Foo $foo =3D null" can ever mean *someth=
ing different* from "?Foo $foo =3D null", it would just be an error=2E

Maybe in 10 years' time we'll have another bonfire of unused features, and=
 this might be one, but it's not something we can plan for right now=2E

Regards,

--=20
Rowan Collins
[IMSoP]