Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117163
Message-ID: <5494eaa7-2fa6-8364-9683-a2c8c9789d81@gmail.com>
Date: Mon, 28 Feb 2022 17:40:51 +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>
In-Reply-To: <983552d8-11f1-b5bc-fb82-148347982fda@gmx.de>
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 21-02-2022 10:04, Christoph M. Becker wrote:
> That "inconsistency" had been introduced with PHP 7.0.0, i.e. right when
> scalar type declarations have been introduced.  Passing a null to a
> non-nullable parameter of a *userland* function throws a TypeError:
> <https://3v4l.org/lbF4h>.  As of PHP 8.1.0, internal functions behave
> the same as userland function in this regard.
> 

In my view, consistency between internal and userland functions brings a 
lot of value, and not only for the language itself. As soon as internal 
and userland become fully consistent it will become a lot easier to 
write "internal" functions in PHP rather than C. Not only will that make 
developing the standard library easier, it may also make the optimizer 
and JIT compiler more effective. The more consistency the better.

Approaches 2 and 3 from the RFC are a step in the right direction.

Regards,
Dik Takken