Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127952
Message-ID: <c72c7936-6c17-4f18-bd19-ae8e40b05507@gmail.com>
Date: Mon, 7 Jul 2025 21:53:32 +0200
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] Deprecations for PHP 8.5
To: "internals@lists.php.net" <internals@lists.php.net>
References: <hzKdzBWWITU1ePjv3qcyK-OzroFAkWst9MQBw2zvKSA8pk1iqruLZZWTTh9gYDo2QX8EY_PiirVYDuwne2Upr3GlqZk570wtLOF49aaP-HQ=@gpb.moe>
 <eb03c51b-344f-4d6d-9e73-7e499b43a928@gmail.com>
 <BL4P223MB13649BEF1496C8BC64F77B43DE4FA@BL4P223MB1364.NAMP223.PROD.OUTLOOK.COM>
Content-Language: en-US
In-Reply-To: <BL4P223MB13649BEF1496C8BC64F77B43DE4FA@BL4P223MB1364.NAMP223.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
From: dossche.niels@gmail.com (Niels Dossche)

On 07/07/2025 20:55, Theodore Brown wrote:
> On Fri, July 4, 2025 at 01:01 Niels Dossche wrote:
> 
>> There are a few things I will vote no for:
>>
>> * Deprecate semicolon after case in switch statement.
>>   People seem to use this and it doesn't seem harmful to have. Just because you don't like it doesn't mean we should yeet it.
> 
> Can you point to a project in current use where this syntax is intentionally used? I searched quite extensively
> (even well beyond the top 1000 Composer packages where there are zero usages) and only found a tiny number of
> accidental usages (e.g. where all the cases in a switch statement had a normal colon except one which had a semicolon typo).
> Almost all of these were quickly fixed by sending a pull request.

See https://externals.io/message/126000, in particular Derick's reply.
Also I'm sure there's a lot of brownfield PHP code that we have no idea about how it looks like.
> Maybe the unnecessary legacy syntax doesn't seem harmful, but I disagree. Non-standard alternate syntax can cause confusion
> about a potential behavioral difference, and sometimes can even hold back future features (for example, deprecating the curly
> brace array access syntax in PHP 7.4 made it possible to implement property hooks in PHP 8.4).
Sure, but whether it opens up anything useful in the future is highly speculative.

> I updated the RFC to document the planned deprecation message, as well a command which automatically fixes any usages in a project.

:+1:

Kind regards
Niels