Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123407
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] [Discussion] Implicitly backed enums
Date: Thu, 23 May 2024 07:30:40 +0700
Message-ID: <4BF0CC62-09A0-4147-A9C1-F0914B31A4B4@koalephant.com>
References: <cff5f1a4-c7e7-4342-9ab5-8c3ff1a9ad40@app.fastmail.com>
Cc: php internals <internals@lists.php.net>
In-Reply-To: <cff5f1a4-c7e7-4342-9ab5-8c3ff1a9ad40@app.fastmail.com>
To: Larry Garfield <larry@garfieldtech.com>
From: php-lists@koalephant.com (Stephen Reay)


Sent from my iPhone

> On 23 May 2024, at 03:58, Larry Garfield <larry@garfieldtech.com> wrote:
>=20
> =EF=BB=BFOn Wed, May 22, 2024, at 2:29 AM, Stephen Reay wrote:
>>>> On 22 May 2024, at 07:58, Larry Garfield <larry@garfieldtech.com> wrote=
:
>>>=20
>>> given that the casing for an enum should be CamelCase (per PER-CS)
>>=20
>> Hi Larry;
>>=20
>> I find myself yet again having to ask that php policies/discussions not
>> revolve around the idea that PHP-FIG is a required/expected part of PHP
>> usage.
>>=20
>> Until a PHP RFC specifying "proper" casing for userland enums passes,
>> can we leave the claims about what they "should be" out of discussions
>> about language/stdlib functionality?
>=20
> 1. The status quo in the ecosystem is relevant to language development.  FI=
G is a part of that ecosystem.  "Everyone in Laravel does X" or "this would b=
reak Symfony which does Y" are also a relevant observation to make, though i=
n neither case is it a binding dictat, of course.  By a similar token, the l=
anguage doesn't require class-per-file, but the de facto standard for virtua=
lly every project that isn't WordPress is to use class-per-file for autoload=
ing.  It would be highly stupid of us to ignore that fact when discussing au=
toloader improvements.
>=20
> 2. The Enum RFC used PascalCase.  The PHP maual uses PascalCase.  We're al=
ready recommending PascalCase as the standard for enum cases.
>=20
> Those who aren't following that recommendation are, from what I've seen, u=
sing ALL_CAPS.  Meaning using lower_case is NOT typical, and thus the issue I=
 mentioned (that automatically using the case name as the backing string nam=
e may not be all that useful) is present either way.
>=20
> --Larry Garfield
>=20

Hi Larry,

I didn't say the community or common uses should be ignored. I just asked yo=
u not to use the phrase "X should be Y because of <external entity>".

It suggests authority where none exists.


Cheers

Stephen=20