On 13-9-2023 17:48, Ben Ramsey wrote:
On 9/10/23 20:59, Juliette Reinders Folmer wrote:
With the above in mind, I wonder how much confusion/code churn
renaming existing classes will cause and if that's worth it,
especially as the suggested case for the PHP native class will likely
be
Hi
On 9/11/23 01:57, Ben Ramsey wrote:
Since class names in PHP aren't case-sensitive, there should be no BC
concerns for changing existing classes to fit this new casing (for
Reflection, debug, and documentation purposes). That is, if we wanted to
also update all existing class names in PHP
On 9/10/23 20:59, Juliette Reinders Folmer wrote:
With the above in mind, I wonder how much confusion/code churn renaming
existing classes will cause and if that's worth it, especially as the
suggested case for the PHP native class will likely be determined by the
version on which the tooling
On 11-9-2023 1:57, Ben Ramsey wrote:
I agree. Using uppercase for the first letter in an acronym and
lowercase for subsequent letters appears to be prevalent in many
userland libraries, so it seems to be what users expect.
Since class names in PHP aren't case-sensitive, there should be no BC
On 8/31/23 13:34, Niels Dossche wrote:
Hi Tim
On 30/08/2023 13:43, Tim Düsterhus wrote:
Hi
after suggesting the use of ucfirst(strtolower(...)) casing for acronyms within
a classname of a draft RFC, I was made aware of previous class naming RFC (June
2017) that required the use of
Hi Tim
On 30/08/2023 13:43, Tim Düsterhus wrote:
> Hi
>
> after suggesting the use of ucfirst(strtolower(...)) casing for acronyms
> within a classname of a draft RFC, I was made aware of previous class naming
> RFC (June 2017) that required the use of PascalCase for class names, with the
>
On Wed, Aug 30, 2023 at 1:44 PM Tim Düsterhus wrote:
> Hi
>
> after suggesting the use of ucfirst(strtolower(...)) casing for acronyms
> within a classname of a draft RFC, I was made aware of previous class
> naming RFC (June 2017) that required the use of PascalCase for class
> names, with the
