Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117085
Message-ID: <983552d8-11f1-b5bc-fb82-148347982fda@gmx.de>
Date: Mon, 21 Feb 2022 10:04:16 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.6.1
Content-Language: de-DE
To: Craig Francis <craig@craigfrancis.co.uk>,
 PHP internals <internals@lists.php.net>
References: <CAFv4g+Efz-V5V1uUedXpusNw6z-on=TT3kdWgC66SptSd8kB4g@mail.gmail.com>
 <CAFv4g+GDsq=w7qtSOVptEBiTTDZk2aeFCVGThVBR=0-xk=0oAA@mail.gmail.com>
In-Reply-To: <CAFv4g+GDsq=w7qtSOVptEBiTTDZk2aeFCVGThVBR=0-xk=0oAA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Allowing NULL for some internal functions
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 20.02.2022 at 21:38, Craig Francis wrote:

> On Sat, 1 Jan 2022 at 23:17, Craig Francis <craig@craigfrancis.co.uk> wr=
ote:
>
>> Draft RFC:
>> https://wiki.php.net/rfc/allow_null
>>
>
>
> I've been over-complicating this... why should NULL be treated so
> differently?
>
> <?php
>   $values =3D ['a', 1, 2.3, false, NULL];
>   foreach ($values as $value) {
>     echo urlencode($value);
>   }
> ?>
>
> It just struck me, this whole thing is about type coercion when not usin=
g
> `strict_types=3D1`; and the 8.1 change has introduced an inconstancy by
> deprecating the coercion of NULL, a frequently used value.

That "inconsistency" had been introduced with PHP 7.0.0, i.e. right when
scalar type declarations have been introduced.  Passing a null to a
non-nullable parameter of a *userland* function throws a TypeError:
<https://3v4l.org/lbF4h>.  As of PHP 8.1.0, internal functions behave
the same as userland function in this regard.


=2D-
Christoph M. Becker