Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121622
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
Date: Thu, 9 Nov 2023 14:58:45 +0000
References: <CAFv4g+EqzB7whakuN-sr6YL2ih9xhHPzCsvTsEgJKMXBh9H9wQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
In-Reply-To: <CAFv4g+EqzB7whakuN-sr6YL2ih9xhHPzCsvTsEgJKMXBh9H9wQ@mail.gmail.com>
Message-ID: <5144806E-E21F-4AF8-B9A2-0161561A6B9E@craigfrancis.co.uk>
Subject: Re: Passing null to parameter
From: craig@craigfrancis.co.uk (Craig Francis)

On 29 Oct 2023, at 11:02, Craig Francis <craig@craigfrancis.co.uk> =
wrote:
> I'm getting really annoyed at the "Passing null to parameter" problem,


As I'm getting the usual negative response (-3), should I write an RFC =
to deprecate NULL coercion in all contexts?

At the moment it's weird that `print($nullable)` isn't deprecated.

And it's weird that I can do `htmlspecialchars('Hi ' . $nullable)` but =
not `'Hi ' . htmlspecialchars($nullable)`.

We might as well make the PHP 9 upgrade as hard as possible, just to =
force a little bit of `strict_types=3D1` on everyone.

Craig=