Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123003
Message-ID: <4c56763c-2d65-4f64-b1ef-87e6ab88a473@bastelstu.be>
Date: Sat, 6 Apr 2024 18:01:55 +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>
 <8c650dbe-4ba6-4f27-beb2-0f63a752b024@bastelstu.be>
 <A27D8F2E-3BBB-4621-A58E-EF40F4F40762@sakiot.com>
Content-Language: en-US
In-Reply-To: <A27D8F2E-3BBB-4621-A58E-EF40F4F40762@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:54, Saki Takamachi wrote:
> However, in the example from "RFC: Namespaces in bundled PHP extensions", the acronyms are not camelcased. e.g. `FFI\FFI`, `OpenSSL`
> In other words, the RFC can be interpreted as "excluding acronyms" implicitly.

This is correct, because the current class naming policy specifies that 
acronyms must be written in UPPERCASE. Thus the examples are consistent 
with the current policy.

> Just to clarify: I agree with your RFC. However, I think it is best to avoid vague statements where the meaning changes depending on interpretation, if possible.

I've added namespaced examples:

https://wiki.php.net/rfc/class-naming-acronyms?do=diff&rev2%5B0%5D=1712350524&rev2%5B1%5D=1712419286&difftype=sidebyside

> In fact, due to some ambiguity in the namespace RFC, I couldn't decide whether BCMath's namespace should be "BcMath" or "BCMath”.

With the current policy it should be "BCMath", if my RFC passes it 
should be "BcMath". I think Bcmath would be fine as well, if you 
consider the extension name to be a single word.

Best regards
Tim Düsterhus