Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117574 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 50843 invoked from network); 22 Apr 2022 19:13:33 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 22 Apr 2022 19:13:33 -0000 To: internals@lists.php.net Date: Fri, 22 Apr 2022 21:47:52 +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: <6261d073.1c69fb81.a42c.d7cfSMTPIN_ADDED_MISSING@mx.google.com> <6262e219.1c69fb81.f1cd4.6ff5SMTPIN_ADDED_MISSING@mx.google.com> 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] [VOTE] Undefined Property Error Promotion From: marandall@php.net (Mark Randall) Message-ID: On 22/04/2022 21:30, Rowan Tommins wrote: > Do you not have even a little bit of hope that we could make that less > confusing, since we're breaking everyone's old code anyway? I seem to remember we had a discussion years ago about deleting unset on properties, but it was being used for a very popular proxy manager to force them to be routed to __get. The rule that anything typed must be initialized, nullable or not, is clearish enough. You could special case nullable, but then it's an extra rule to learn beyond "typed = needs to be initialized".