On Sunday, April 26, 2015, Levi Morrison <le...@php.net (mailto:le...@php.net)> wrote: > On Sat, Apr 25, 2015 at 8:27 PM, Nate Abele <nate.ab...@gmail.com > (javascript:;)> wrote: > >> Dear Internals, > >> > >> I would like to discuss a small RFC for reserving more types in PHP 7: > >> https://wiki.php.net/rfc/reserve_more_types_in_php_7 > > > > > > Welp, thanks for breaking my framework, everyone. > > > > It just *had* to be case-insensitive too, hm? > > I'm not sure what you want us to say.
Well, it looks to me like all the discussion is around preventing class and namespace names like “string”, “float”, etc. Granted, PHP class names are case-insensitive, but how hard would it be to reserve these in a case-sensitive way? Lithium, CakePHP, and Drupal all have String classes. These aren’t small projects. Not to mention the presumably untold numbers of developers who have hand-rolled ‘type’ classes into their projects while waiting around for scalar type-hinting support to land. And everyone’s cool with breaking all of these? Has someone valiantly signed on to do LTS support for 5.6 beyond two years from now, and I’m just not aware of it? Or are we cool with letting all the dependent software that can’t afford to be upgraded just atrophy and die? I get that PHP 7 is the big opportunity to break backward compatibility, but yeesh, really? It’s like we’re not even trying anymore.
