Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117193
Message-ID: <4bff3f23-a3ec-4416-f44e-1f4f5d7e0caa@gmail.com>
Date: Wed, 2 Mar 2022 13:26:16 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.6.1
Content-Language: en-US
To: internals@lists.php.net
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>
 <CAC5V6gjianVuPo654_-mETYxsu0-eSo++Ez1yy81MNEcfwFq1Q@mail.gmail.com>
 <69642616-72b7-44fe-97a7-27ae03bc8fce@www.fastmail.com>
 <CAFv4g+F0HOgCgeUyiG06qhxQnWbVCN2aaP=a2CJT9tkbMP7kLg@mail.gmail.com>
 <7fbed755-42e2-d023-285f-39863a97f297@gmx.de>
 <3665C848-B4C3-4528-AEFA-02C868748AA8@cschneid.com>
 <0b5bc29d-3814-0e1d-b94a-47790019c778@gmx.de>
 <CAFv4g+HPm+edmgnPAGwBk=4EJxj2can--iWfgtMasrYHk6pLww@mail.gmail.com>
In-Reply-To: <CAFv4g+HPm+edmgnPAGwBk=4EJxj2can--iWfgtMasrYHk6pLww@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Allowing NULL for some internal functions
From: dik.takken@gmail.com (Dik Takken)

On 01-03-2022 19:10, Craig Francis wrote:
> 
> I'm pretty confident the best solution is to keep all parameter types the
> same (I could argue that some parameters could do with a "cannot be empty"
> exception, to reject NULL and an Empty String, but that would be a
> different RFC)... and anyone using `strict_types` will still have a Type
> Error when they pass a value of the wrong type to these parameters... the
> *only* change is for those not using `strict_types`, for NULL to still be
> coerced to a string/int/float/bool, as it always has been for internal
> functions... and I think this can be done to user functions as well, as
> developers not using strict_types won't have cared about this before.
> 
> Craig
> 

Hi Craig,

So, to get this crystal clear, this is my understanding of what you are 
proposing for passing null to a non-nullable function parameter 
(hopefully my ASCII art will come through ok):


which     | strict_types  | PHP 8.0    | PHP 8.1    | PHP 9
----------|---------------|------------|------------|----------
user      | 1             | TypeError  | TypeError  | TypeError
internal  | 1             | TypeError  | TypeError  | TypeError
user      | 0             | TypeError  | TypeError  | coerced
internal  | 0             | coerced    | Deprecated | coerced

Is this correct?

Regards,
Dik Takken