Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117080
MIME-Version: 1.0
References: <CAFv4g+Efz-V5V1uUedXpusNw6z-on=TT3kdWgC66SptSd8kB4g@mail.gmail.com>
In-Reply-To: <CAFv4g+Efz-V5V1uUedXpusNw6z-on=TT3kdWgC66SptSd8kB4g@mail.gmail.com>
Date: Sun, 20 Feb 2022 20:38:17 +0000
Message-ID: <CAFv4g+GDsq=w7qtSOVptEBiTTDZk2aeFCVGThVBR=0-xk=0oAA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007097ff05d8791939"
Subject: Re: [PHP-DEV] Allowing NULL for some internal functions
From: craig@craigfrancis.co.uk (Craig Francis)

--0000000000007097ff05d8791939
Content-Type: text/plain; charset="UTF-8"

On Sat, 1 Jan 2022 at 23:17, Craig Francis <craig@craigfrancis.co.uk> wrote:

> Draft RFC:
> https://wiki.php.net/rfc/allow_null
>


I've been over-complicating this... why should NULL be treated so
differently?

<?php
  $values = ['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 using
`strict_types=1`; and the 8.1 change has introduced an inconstancy by
deprecating the coercion of NULL, a frequently used value.

Craig

--0000000000007097ff05d8791939--