Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117167
MIME-Version: 1.0
References: <CAFv4g+Efz-V5V1uUedXpusNw6z-on=TT3kdWgC66SptSd8kB4g@mail.gmail.com>
 <CAFv4g+GDsq=w7qtSOVptEBiTTDZk2aeFCVGThVBR=0-xk=0oAA@mail.gmail.com>
 <983552d8-11f1-b5bc-fb82-148347982fda@gmx.de> <5494eaa7-2fa6-8364-9683-a2c8c9789d81@gmail.com>
In-Reply-To: <5494eaa7-2fa6-8364-9683-a2c8c9789d81@gmail.com>
Date: Mon, 28 Feb 2022 19:41:25 +0000
Message-ID: <CAFv4g+HBkgSH5UimqKYY63o24C2soW+yQ1Us+QBSn31R2VvgZQ@mail.gmail.com>
To: Dik Takken <dik.takken@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000008dfdbb05d9193c83"
Subject: Re: [PHP-DEV] Allowing NULL for some internal functions
From: craig@craigfrancis.co.uk (Craig Francis)

--0000000000008dfdbb05d9193c83
Content-Type: text/plain; charset="UTF-8"

On Mon, 28 Feb 2022 at 16:41, Dik Takken <dik.takken@gmail.com> wrote:

> In my view, consistency between internal and userland functions brings a
> lot of value, and not only for the language itself.



Thanks Dik,

I agree that consistency is very important, and I do not want to stop
that... I just recognise that many scripts use NULL coercion a lot, as they
do with other variable types (when not using `strict_types=1`), and that's
being broken just for NULL (which creates a form of inconsistency vs
int/float/string/bool types).

I started with preferring 2, but I think 1 is the best route to keep the
spirit of the original RFC, while not breaking backwards compatibility.

Craig

--0000000000008dfdbb05d9193c83--