Re: [RFC] Casing of acronyms in class and method names
| From: | Derick Rethans | Date: | Tue, 16 Apr 2024 16:13:02 +0000 |
| Subject: | Re: [RFC] Casing of acronyms in class and method names | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-123140@lists.php.net to get a copy of this message | ||
On Fri, 5 Apr 2024, Tim Düsterhus wrote:
> Hi
>
> I've just written up the follow-up RFC to my previous “Casing of acronyms in
> class and method names” thread and I'm officially opening up the discussion
> period for it.
One example is the PCGOneseq128XSLRR64 mentioned above
That is probably not the best example of a "readable" class name, as no
matter the casing, it's not readable :-)
None, yet. This RFC will result in changes to:
The
https://github.com/php/php-src/blob/536305436f44e91731bc5c86e06f137e44a01109/CODING_STANDARDS.md#L173-L211
document should probably be folded into
https://github.com/php/policies/blob/main/coding-standards-and-naming.rst
— having it in two places isn't great.
cheers,
Derick
--
https://derickrethans.nl | https://xdebug.org | https://dram.io
Author of Xdebug. Like it? Consider supporting me: https://xdebug.org/support
mastodon: @derickr@phpc.social @xdebug@phpc.social