Re: Allowing NULL for some internal functions
| From: | Craig Francis | Date: | Mon, 28 Feb 2022 19:41:25 +0000 |
| Subject: | Re: Allowing NULL for some internal functions | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-117167@lists.php.net to get a copy of this message | ||
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