On Friday, 5 April 2024 at 18:00, Tim Düsterhus <t...@bastelstu.be> 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. > > Please find the following links for your convenience: > > 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 > 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 the casing of existing classes? This isn't a BC Break in theory as class names are, for the time being, case-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
