Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86000 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80748 invoked from network); 28 Apr 2015 20:15:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Apr 2015 20:15:21 -0000 Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:10654] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0D/A0-08579-85AEF355 for ; Tue, 28 Apr 2015 16:15:21 -0400 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 1DB344B02A6; Tue, 28 Apr 2015 22:14:57 +0200 (CEST) Reply-To: To: "'Levi Morrison'" Cc: "'Dennis Birkholz'" , "'internals'" References: <553DBEC4.7000609@gmail.com> <006c01d081a7$0e600640$2b2012c0$@php.net> <553F81DD.6020506@birkholz.biz> <007a01d081bd$75ada260$6108e720$@php.net> In-Reply-To: Date: Tue, 28 Apr 2015 22:15:13 +0200 Message-ID: <008901d081f0$09c98400$1d5c8c00$@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJH4NXmYqiUFTwX4N+eJK7dHOGqJgGFwxK9AWEuISgCX5oKXgGIIOFyAVu0O9EB601yTwEuJFkrnBn+ggA= Content-Language: fr X-Antivirus: avast! (VPS 150428-0, 28/04/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Re: [RFC] Reserving More Types in PHP 7 From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) > De : morrison.levi@gmail.com [mailto:morrison.levi@gmail.com] De la = part > > 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. >=20 > 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). Mmh, PHP 7 or not, the reaction was really : 'huge BC break for no = benefit'. I'll try to propose it more in advance for 8.0, as you = suggest, but I'm really not sure it has more success. Anyway, that's not = a serious solution to solve type hint conflicts. Regards Fran=C3=A7ois