On Tue, Jun 16, 2026, at 7:03 PM, Jorg Sowa wrote: > Hello internals, > I would like to revive the discussion about fully case-sensitive PHP. I > have collected the points raised in previous discussions, and browsed > all affected language features and functionalities. > > I still need to perform the impact analysis and the performance > benchmarks. I will add them to the RFC and inform in the thread when I > complete it. > > RFC: https://wiki.php.net/rfc/case_sensitive_php > > Kind regards, > Jorg
Is there a practical, real-world issue this solves? I have never in my life seen someone write STRLEN(). Drupal used to use TRUE/FALSE instead of true/false, but I don't know if they've ever changed that and it doesn't hurt anything. Class names everyone should already be treating as case sensitive because of the file system. And IDEs and SA tools have been pushing toward the "standard" casing of things for decades. I don't really see this as an issue to solve. But I can see where it could cause issues when making dynamic method calls, like $controller->$httpMethod($request), which is something a number of smaller frameworks have done for years. So I'm -1 at this point. --Larry Garfield
