Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118011
MIME-Version: 1.0
References: <CAMs36HcGzvwwTTU+nUO+U_M6o4qpOAHES7RbHEJWm6iot+-9=Q@mail.gmail.com>
 <CAC5V6gj04Qi7C-4UCXeF003u_jKUT9cuqTD8xzPQ06CDMJhURw@mail.gmail.com>
In-Reply-To: <CAC5V6gj04Qi7C-4UCXeF003u_jKUT9cuqTD8xzPQ06CDMJhURw@mail.gmail.com>
Date: Mon, 20 Jun 2022 16:36:49 +0200
Message-ID: <CANS-=pdDZJ+8yndFmebPZu5S3VXjFr-OW93ndpbkk_+JD9=zxw@mail.gmail.com>
To: Guilliam Xavier <guilliam.xavier@gmail.com>
Cc: Go Kudo <g-kudo@colopl.co.jp>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004b313d05e1e20a35"
Subject: Re: [PHP-DEV] [RFC] [Under Discussion] Random Extension Improvement
From: kjarli@gmail.com (Lynn)

--0000000000004b313d05e1e20a35
Content-Type: text/plain; charset="UTF-8"

On Mon, Jun 20, 2022 at 3:15 PM Guilliam Xavier <guilliam.xavier@gmail.com>
wrote:

> Hi,
>
> > https://wiki.php.net/rfc/random_extension_improvement
>
> Thanks, but I am not sure about your argument in "Classnames are not
> canonicalized": does "PHP applies strict PascalCase to class names"
> (which remains to be proved) really imply to rename *acronyms* (e.g.
> "CombinedLCG" to "CombinedLcg")? especially given existing classes
> like "SimpleXMLElement" (not "SimpleXmlElement"), and that the
> accepted "Class Naming" RFC (https://wiki.php.net/rfc/class-naming)
> voted for "PascalCase except Acronyms" (not "Always PascalCase") --
> excerpts:
>

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.

--0000000000004b313d05e1e20a35--