Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123140
Date: Tue, 16 Apr 2024 17:13:02 +0100 (BST)
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
cc: PHP internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] Casing of acronyms in class and method names
In-Reply-To: <792b2282-b7a3-40dd-899c-daab55353316@bastelstu.be>
Message-ID: <6a56933b-f09b-7226-13da-0ae4a926da1b@php.net>
References: <792b2282-b7a3-40dd-899c-daab55353316@bastelstu.be>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323329-1980713670-1713283982=:26150"
From: derick@php.net (Derick Rethans)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1980713670-1713283982=:26150
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Fri, 5 Apr 2024, Tim D=C3=BCsterhus wrote:

> Hi
>=20
> I've just written up the follow-up RFC to my previous =E2=80=9CCasing of =
acronyms in
> class and method names=E2=80=9D thread and I'm officially opening up the =
discussion
> period for it.

=09One example is the PCGOneseq128XSLRR64 mentioned above

That is probably not the best example of a "readable" class name, as no=20
matter the casing, it's not readable :-)

=09None, yet. This RFC will result in changes to:=20

The=20
https://github.com/php/php-src/blob/536305436f44e91731bc5c86e06f137e44a0110=
9/CODING_STANDARDS.md#L173-L211=20
document should probably be folded into=20
https://github.com/php/policies/blob/main/coding-standards-and-naming.rst=
=20
=E2=80=94 having it in two places isn't great.

cheers,
Derick

--=20
https://derickrethans.nl | https://xdebug.org | https://dram.io

Author of Xdebug. Like it? Consider supporting me: https://xdebug.org/suppo=
rt

mastodon: @derickr@phpc.social @xdebug@phpc.social
--8323329-1980713670-1713283982=:26150--