Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85998
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.178 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <007a01d081bd$75ada260$6108e720$@php.net>
References: <EC598AEEF641411B949D685DF8262B4E@gmail.com>
	<CAFMT4Npcjz9kQjfSrKH3JwoyEUqCE6DzWnAaZ5c_idcuVAQ2fA@mail.gmail.com>
	<A326B86EEE4C4E36B85455E01F355A22@gmail.com>
	<553DBEC4.7000609@gmail.com>
	<006c01d081a7$0e600640$2b2012c0$@php.net>
	<553F81DD.6020506@birkholz.biz>
	<007a01d081bd$75ada260$6108e720$@php.net>
Date: Tue, 28 Apr 2015 11:35:03 -0600
Message-ID: <CAFMT4Npof1QfHTMwrGefEMUrZb=48xceGYbENAGJtE5FEGESTg@mail.gmail.com>
To: "francois@php.net" <francois@php.net>
Cc: Dennis Birkholz <dennis@birkholz.biz>, internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: [RFC] Reserving More Types in PHP 7
From: levim@php.net (Levi Morrison)

On Tue, Apr 28, 2015 at 8:13 AM, Fran=C3=A7ois 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 reject=
ed, most considering it is a *huge* BC break for almost no benefit. I perso=
nally 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 p=
robably implemented as case-insensitive too. In other words, if you're read=
y 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).