Re: Re: [RFC] Reserving More Types in PHP 7
| From: | Levi Morrison | Date: | Tue, 28 Apr 2015 17:35:03 +0000 |
| Subject: | Re: Re: [RFC] Reserving More Types in PHP 7 | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-85998@lists.php.net to get a copy of this message | ||
On Tue, Apr 28, 2015 at 8:13 AM, François Laupretre <francois@php.net> wrote:
>> De : Dennis Birkholz [mailto:dennis@birkholz.biz]
>>
>> I would like PHP to make all class/trait/interface names case-sensitive
>> and use only lower-case names for the scalar type hints (same for
>> object, array, etc.). This would solve most problems. Class names are
>> kind of case sensitive in applications that rely on autoloading on
>> platforms with case sensitive file systems.
>
> 1. I proposed making class names case-sensitive and it was clearly rejected, most considering
> it is a *huge* BC break for almost no benefit. I personally don't know any software which uses
> class names in a case-insensitive manner but it seems others do ! I am not sure, but scalar type
> hints were probably implemented as case-insensitive too. In other words, if you're ready to
> relaunch the case-sensitivity discussion, feel free to do it.
To be completely accurate, it was rejected *for PHP 7*. PHP 7 was
announced suddenly and rushed through. I think a BC break of this
magnitude in PHP 7 would be incredibly painful *because of the
timetable*. Whereas if we decide now that in PHP 8 all identifiers
will be case sensitive that's a different story because of the
timeline. Knowing years in advance that something will happen gives
you ample time to migrate (like we are doing with PHP 4 constructors
in the PHP 7 series; they are deprecated and support will be removed
in PHP 8).