Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120960
MIME-Version: 1.0
References: <01e3ff17-5088-0431-6014-82ef4e4789b2@bastelstu.be>
In-Reply-To: <01e3ff17-5088-0431-6014-82ef4e4789b2@bastelstu.be>
Date: Wed, 30 Aug 2023 13:58:18 +0200
Message-ID: <CANS-=pcsqBZThLNoC5YmuVdHvvZ1UmVq=i+d+F13P6kz-Rbktg@mail.gmail.com>
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000044bb4e060422a631"
Subject: Re: [PHP-DEV] Casing of acronyms in class and method names
From: kjarli@gmail.com (Lynn)

--00000000000044bb4e060422a631
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 30, 2023 at 1:44=E2=80=AFPM Tim D=C3=BCsterhus <tim@bastelstu.b=
e> wrote:

> Hi
>
> after suggesting the use of ucfirst(strtolower(...)) casing for acronyms
> within a classname of a draft RFC, I was made aware of previous class
> naming RFC (June 2017) that required the use of PascalCase for class
> names, with the exception of acronyms which must be completely uppercased=
:
>
> [...]
> 2. It decreases readability.
>
> Especially if multiple acronyms follow each other. One example is the
> PCGOneseq128XSLRR64 mentioned above: It's not clear that XSL
> (XorShiftLow) and RR (RandomlyRotate) are two different acronyms.
>
> Likewise PDOODBC is much harder to parse than PdoOdbc.
>
> Another example might be JavaScript's XMLHttpRequest which incidentally
> mixes both variants. According to the class naming RFC it would need to
> be called XMLHTTPRequest, resulting in 8 consecutive uppercase characters=
.
>

Thanks for bringing this up as readability is indeed an issue for me with
all caps acronyms. I would much prefer Acronyms to be treated as words as
this is how most people seem to use them anyway.

--00000000000044bb4e060422a631--