Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123121
Date: Fri, 12 Apr 2024 12:55:52 +0000
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
Message-ID: <s26cRmY4Vn6t59l9DHQ0iFia-yHyN-jZfKXFHbvpC6x0qo9pGd4YSCv8vNakY05TQYsV6_Seebfe4-ZiiWsaA2ijUJ4rQWz1wlq4A4owEJ8=@gpb.moe>
In-Reply-To: <792b2282-b7a3-40dd-899c-daab55353316@bastelstu.be>
References: <792b2282-b7a3-40dd-899c-daab55353316@bastelstu.be>
Feedback-ID: 96993444:user:proton
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: internals@gpb.moe ("Gina P. Banyard")

On Friday, 5 April 2024 at 18:00, Tim D=C3=BCsterhus <tim@bastelstu.be> wro=
te:

> 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 ope=
ning up
> the discussion period for it.
>=20
> Please find the following links for your convenience:
>=20
> RFC: https://wiki.php.net/rfc/class-naming-acronyms
> Previous ML discussion: https://externals.io/message/120959#120959
> Related discussion in PHP-FIG:
> https://github.com/php-fig/per-coding-style/issues/83
>=20


Thank you for working on this!

I agree that this policy change makes sense.

I was wondering, however, if there should be a follow-up RFC to normalize t=
he casing of existing classes?
This isn't a BC Break in theory as class names are, for the time being, cas=
e-insensitive.
I know in practice that tooling in the ecosystem normalize the names to be =
the one as currently defined, so it might produce diffs depending on which =
version of PHP the tool is ran on.
The output of tests could be affected.

Maybe this change is better suited for PHP 9?


Best regards,

Gina P. Banyard