Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114744 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 16278 invoked from network); 5 Jun 2021 20:21:08 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 5 Jun 2021 20:21:08 -0000 To: internals@lists.php.net References: <7DC82988-16E1-4228-BF94-46E633BD116E@woofle.net> Date: Sat, 5 Jun 2021 21:35:13 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 87.81.129.66 Subject: Re: [PHP-DEV] Disable autovivification on false From: marandall@php.net (Mark Randall) Message-ID: On 05/06/2021 20:50, Kamil Tekiela wrote: > However, I would still like to hear from you whether you > use autovivification from false and/or null in your projects. So far, I was > not able to identify when this would be useful in real-life scenarios. As per the RFC: "In PHP 8.1, appending to a variable of type false will throw a deprecation error" You might want to clarify this language, throwing an error is understood to have a specific meaning in PHP, and it's not what it's doing here. Mark Randall