Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117698 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 52588 invoked from network); 8 May 2022 10:00:04 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 8 May 2022 10:00:04 -0000 To: internals@lists.php.net Date: Sun, 8 May 2022 12:38:17 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Content-Language: en-GB References: <5598bad8-4e1a-7638-d3aa-36b02568d1a8@alec.pl> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 149.241.131.223 Subject: Re: [PHP-DEV] NULL Coercion Consistency From: marandall@php.net (Mark Randall) Message-ID: On 08/05/2022 11:48, Jordan LeDoux wrote: > This is not the case with null. If you use the unset() function on a > variable for example, it will var_dump as null *and* it will pass an > is_null() check *and* it will pass a $var === null *and* it will return > false for an isset() check. Null loses these qualities if it is cast to > *any* scalar. Fortunately the writing is on the wall for the undefined cases, but that doesn't take away from your argument.