Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123001
Message-ID: <8c650dbe-4ba6-4f27-beb2-0f63a752b024@bastelstu.be>
Date: Sat, 6 Apr 2024 17:38:06 +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>
Cc: PHP internals <internals@lists.php.net>
References: <792b2282-b7a3-40dd-899c-daab55353316@bastelstu.be>
 <D735EDA2-2234-4D20-8BFB-E2C76F301AA7@sakiot.com>
Content-Language: en-US
In-Reply-To: <D735EDA2-2234-4D20-8BFB-E2C76F301AA7@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/6/24 17:16, Saki Takamachi wrote:
> Strictly speaking, namespace is neither a class nor a method, so isn't it outside the scope of this RFC? In fact, RFC: Class Naming makes no mention of namespace naming conventions at all. I asked this because there was mention of namespaces in the `DOM`.
> 
> If I'm not misunderstanding something, I think I should clarify that RFCs also include namespaces.

Namespaces are defined as CamelCase (i.e. upper camel case / PascalCase) 
in the “Namespaces in bundled PHP Extensions” RFC:

https://wiki.php.net/rfc/namespaces_in_bundled_extensions#proposal

The phrasing in the RFC is intentionally worded to speak about 
abbreviations and acronyms in a generic way (i.e. not specific to 
classes or methods). It naturally follows that the same rules applies to 
acronyms in namespaces, especially since they are effectively part of a 
class name.

------------------------------

However I agree that it should be incorporated explicitly once the 
existing policies in the policy repository have been cleaned up and 
rewritten as a follow-up to the 
https://wiki.php.net/rfc/policy-repository RFC:

> Once (and if) this RFC is accepted, a first new step would be to rephrase the text so that it reads like a policy document, instead of an RFC. The wording is currently exactly as in the used RFCs, without modification.

That has not yet happened, though.

Best regards
Tim Düsterhus