Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121035
To: internals@lists.php.net
References: <01e3ff17-5088-0431-6014-82ef4e4789b2@bastelstu.be>
 <48699eff-c0d1-43de-b68e-2327fa601528@gmail.com>
Message-ID: <64FE7480.6040505@adviesenzo.nl>
Date: Mon, 11 Sep 2023 03:59:28 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <48699eff-c0d1-43de-b68e-2327fa601528@gmail.com>
Content-Type: multipart/alternative;
 boundary="------------030305000303090304080008"
Subject: Re: [PHP-DEV] Casing of acronyms in class and method names
From: php-internals_nospam@adviesenzo.nl (Juliette Reinders Folmer)

--------------030305000303090304080008
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 11-9-2023 1:57, Ben Ramsey wrote:
> I agree. Using uppercase for the first letter in an acronym and 
> lowercase for subsequent letters appears to be prevalent in many 
> userland libraries, so it seems to be what users expect.
>
> Since class names in PHP aren't case-sensitive, there should be no BC 
> concerns for changing existing classes to fit this new casing (for 
> Reflection, debug, and documentation purposes). That is, if we wanted 
> to also update all existing class names in PHP that contain acronyms 
> (e.g., DOMDocument -> DomDocument, SimpleXMLElement -> 
> SimpleXmlElement, etc.).
>

This prevalence may stem from various CS checks enforcing/suggesting the 
naming like that based on their implementation/interpretation of 
CamelCaps name checks, often related to PSR4.

Along the same lines, I'm aware of CS-like tools enforcing the use of 
PHP native class names to be in the case as defined in PHP (mostly to 
prevent confusion when people search for more info on the class and 
such, even though it doesn't matter for the actual use).

With the above in mind, I wonder how much confusion/code churn renaming 
existing classes will cause and if that's worth it, especially as the 
suggested case for the PHP native class will likely be determined by the 
version on which the tooling is being run. I.e. tool being run on PHP 
8.2 suggest DOMDocument, tool being run on PHP 8.4 would flag 
DOMDocument and suggest DomDocument...

Smile,
Juliette

--------------030305000303090304080008--