Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118015
Message-ID: <35b15014-b22c-7f7a-a061-ef5ccdb80a54@bastelstu.be>
Date: Mon, 20 Jun 2022 17:22:52 +0200
MIME-Version: 1.0
Content-Language: en-US
To: Lynn <kjarli@gmail.com>
Cc: PHP internals <internals@lists.php.net>
References: <CAMs36HcGzvwwTTU+nUO+U_M6o4qpOAHES7RbHEJWm6iot+-9=Q@mail.gmail.com>
 <CAC5V6gj04Qi7C-4UCXeF003u_jKUT9cuqTD8xzPQ06CDMJhURw@mail.gmail.com>
 <CANS-=pdDZJ+8yndFmebPZu5S3VXjFr-OW93ndpbkk_+JD9=zxw@mail.gmail.com>
In-Reply-To: <CANS-=pdDZJ+8yndFmebPZu5S3VXjFr-OW93ndpbkk_+JD9=zxw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Acronyms in class names (was: [RFC] [Under Discussion] Random
 Extension Improvement)
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=c3=bcsterhus?=)

Hi

On 6/20/22 16:36, Lynn wrote:
> Not specifically directed at this discussion, but perhaps this needs a
> revision. HTTPStatus is much harder to read for me than HttpStatus and it's
> unclear where the boundary of an acronym starts or stops. If anyone ever
> decides to make an RFC for this, you have my vote. These Acronyms are
> treated as words and thus should follow the same naming convention. If they
> shouldn't be treated as words, write their full name:
> HypertextTransferProtocolStatus.
> 

Yes, I agree here. I switched to ucfirst(strtolower()) acronyms a while 
ago and find those much more readable. It also avoids issues when there 
are multiple acronyms within a single identifier (think PCGRNG vs PcgRng).

Best regards
Tim Düsterhus