Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108055 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 61043 invoked from network); 9 Jan 2020 16:00:20 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 9 Jan 2020 16:00:20 -0000 To: internals@lists.php.net References: <3b392441-9987-ef36-195e-214bbb50406f@php.net> Date: Thu, 9 Jan 2020 14:06:00 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 In-Reply-To: <3b392441-9987-ef36-195e-214bbb50406f@php.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 78.105.135.63 Subject: Re: [PHP-DEV] Warn when declaring required parameter after optionalone From: marandall@php.net (Mark Randall) Message-ID: On 09/01/2020 12:31, Sebastian Bergmann wrote: > I would prefer erroring out over just emitting a warning. I'm in agreement with Sebastian, a compile time error is the way to go. I could understand a warning or deprecation in a minor release, but as there's already so many engine level exceptions landing in 8.0, I think it makes sense to throw this on the pile as well to be swept up in the same pass of migrations that people do in preperation for 8.0. Better to get the pain over and done with, rather than drag it out over multiple versions, as I'd guess that even if it was a warning now, it would end up a compile error a few years from now. -- Mark Randall