Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123412
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-480-g515a2f54a-fm-20240515.001-g515a2f54
Precedence: bulk
MIME-Version: 1.0
Message-ID: <a5b9b837-19fd-4644-b45e-12aa1b66b560@app.fastmail.com>
In-Reply-To: <4BF0CC62-09A0-4147-A9C1-F0914B31A4B4@koalephant.com>
References: <cff5f1a4-c7e7-4342-9ab5-8c3ff1a9ad40@app.fastmail.com>
 <4BF0CC62-09A0-4147-A9C1-F0914B31A4B4@koalephant.com>
Date: Thu, 23 May 2024 07:58:24 -0500
To: "php internals" <internals@lists.php.net>
Subject: Re: [PHP-DEV] [Discussion] Implicitly backed enums
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: larry@garfieldtech.com ("Larry Garfield")

On Wed, May 22, 2024, at 7:30 PM, Stephen Reay wrote:
> Sent from my iPhone
>
>> On 23 May 2024, at 03:58, Larry Garfield <larry@garfieldtech.com> wro=
te:
>>=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 discussio=
ns
>>> about language/stdlib functionality?
>>=20
>> 1. The status quo in the ecosystem is relevant to language developmen=
t.  FIG is a part of that ecosystem.  "Everyone in Laravel does X" or "t=
his would break Symfony which does Y" are also a relevant observation to=
 make, though in neither case is it a binding dictat, of course.  By a s=
imilar token, the language doesn't require class-per-file, but the de fa=
cto standard for virtually every project that isn't WordPress is to use =
class-per-file for autoloading.  It would be highly stupid of us to igno=
re that fact when discussing autoloader improvements.
>>=20
>> 2. The Enum RFC used PascalCase.  The PHP maual uses PascalCase.  We'=
re already recommending PascalCase as the standard for enum cases.
>>=20
>> Those who aren't following that recommendation are, from what I've se=
en, using ALL_CAPS.  Meaning using lower_case is NOT typical, and thus t=
he issue I mentioned (that automatically using the case name as the back=
ing string name 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=20
> asked you not to use the phrase "X should be Y because of <external=20
> entity>".
>
> It suggests authority where none exists.

I think you're reading far more "intent" or "enforcement" into my parent=
hetical than was intended or appropriate.

--Larry Garfield