Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123127
Message-ID: <c9050bbd-954f-4dbe-9e1e-e303adb7722f@bastelstu.be>
Date: Sun, 14 Apr 2024 17:03:28 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Casing of acronyms in class and method names
To: Saki Takamachi <saki@sakiot.com>, "Gina P. Banyard" <internals@gpb.moe>
Cc: PHP internals <internals@lists.php.net>
References: <s26cRmY4Vn6t59l9DHQ0iFia-yHyN-jZfKXFHbvpC6x0qo9pGd4YSCv8vNakY05TQYsV6_Seebfe4-ZiiWsaA2ijUJ4rQWz1wlq4A4owEJ8=@gpb.moe>
 <5ECDDF78-FBCB-4D81-A4CD-F64DAEE27559@sakiot.com>
Content-Language: en-US
In-Reply-To: <5ECDDF78-FBCB-4D81-A4CD-F64DAEE27559@sakiot.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 4/12/24 15:53, Saki Takamachi wrote:
>> This isn't a BC Break in theory as class names are, for the time being, case-insensitive.
> 
> Strictly speaking, this can be considered a BC Break because the string returned by `::class` changes.
> However, I'm not sure how much of an impact it will have.

Indeed. See my email in the previous pre-RFC discussion thread: 
https://news-web.php.net/php.internals/121057

Best regards
Tim Düsterhus