Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123406
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: <cff5f1a4-c7e7-4342-9ab5-8c3ff1a9ad40@app.fastmail.com>
In-Reply-To: <3053F28C-22BB-40B2-9675-05742E5EB8BB@koalephant.com>
References: <9c763cee-6524-4423-b95e-6bfff4763d2e@app.fastmail.com>
 <3053F28C-22BB-40B2-9675-05742E5EB8BB@koalephant.com>
Date: Wed, 22 May 2024 20:46:22 +0000
To: "php internals" <internals@lists.php.net>
Subject: Re: [PHP-DEV] [Discussion] Implicitly backed enums
Content-Type: text/plain
From: larry@garfieldtech.com ("Larry Garfield")

On Wed, May 22, 2024, at 2:29 AM, Stephen Reay wrote:
>> On 22 May 2024, at 07:58, Larry Garfield <larry@garfieldtech.com> wrote:
>> 
>> given that the casing for an enum should be CamelCase (per PER-CS)
>
> Hi Larry;
>
> 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. 
>
> 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?

1. The status quo in the ecosystem is relevant to language development.  FIG is a part of that ecosystem.  "Everyone in Laravel does X" or "this 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 similar token, the language doesn't require class-per-file, but the de facto 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 ignore that fact when discussing autoloader improvements.

2. The Enum RFC used PascalCase.  The PHP maual uses PascalCase.  We're already recommending PascalCase as the standard for enum cases.

Those who aren't following that recommendation are, from what I've seen, using 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 name may not be all that useful) is present either way.

--Larry Garfield