Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118016
Message-ID: <376a90af-8709-012c-76ee-fa351d1b017c@gmx.de>
Date: Mon, 20 Jun 2022 17:25:25 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.10.0
Content-Language: de-DE
To: Go Kudo <zeriyoshi@gmail.com>, Lynn <kjarli@gmail.com>,
 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>
 <CABTDVhBY3L87PNyT9OZ72PN90qQ6C1Ngz8YRJYuTsqgpkrnNug@mail.gmail.com>
In-Reply-To: <CABTDVhBY3L87PNyT9OZ72PN90qQ6C1Ngz8YRJYuTsqgpkrnNug@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] [Under Discussion] Random Extension Improvement
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 20.06.2022 at 16:44, Go Kudo wrote:

> 2022=E5=B9=B46=E6=9C=8820=E6=97=A5(=E6=9C=88) 23:37 Lynn <kjarli@gmail.c=
om>:
>
>> On Mon, Jun 20, 2022 at 3:15 PM Guilliam Xavier <guilliam.xavier@gmail.=
com
>> wrote:
>>
>>>> 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 eve=
r
>> 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.
>
> I support "PascalCase except Acronyms" for readability, but would like t=
o
> see this
> clarified as I get very lost when implementing new features.
> I think it is necessary because I expect various OO APIs will be added i=
n
> the future,
> like cURL.

In my opinion, <https://wiki.php.net/rfc/class-naming> was a bit
unfortunate.  It may have been better to decide on a case by case basis.

For instance, we have introduced several Curl* classes in PHP 8.0[1],
and these adhere to the appropriate example in the RFC, although CURL is
clearly an acronym[2], and the canonical spelling is even cURL.  Maybe
even worse, the previously introduced CURLFile[3] uses different
capitalization, and CURLStringFile[4] which was introduced in PHP 8.1 is
aligned to that spelling.

So, obviously, the RFC didn't have a good impact on some of the namings
so far.

[1] <https://www.php.net/curl>
[2] <https://curl.se/docs/faq.html#What_is_cURL>
[3] <https://www.php.net/manual/en/class.curlfile.php>
[4] <https://www.php.net/manual/en/class.curlstringfile.php>

=2D-
Christoph M. Becker