Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85996 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56995 invoked from network); 28 Apr 2015 14:13:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Apr 2015 14:13:16 -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:48232] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2E/27-17556-C759F355 for ; Tue, 28 Apr 2015 10:13:16 -0400 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 794154B02BD; Tue, 28 Apr 2015 16:12:55 +0200 (CEST) Reply-To: To: "'Dennis Birkholz'" , References: <553DBEC4.7000609@gmail.com> <006c01d081a7$0e600640$2b2012c0$@php.net> <553F81DD.6020506@birkholz.biz> In-Reply-To: <553F81DD.6020506@birkholz.biz> Date: Tue, 28 Apr 2015 16:13:11 +0200 Message-ID: <007a01d081bd$75ada260$6108e720$@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+eJK7dHOGqJgGFwxK9AWEuISgCX5oKXgGIIOFyAVu0O9GcMmFwgA== 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 : Dennis Birkholz [mailto:dennis@birkholz.biz] >=20 > 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. 2. Anyway, basing name conflict resolution on naming conventions is not = acceptable, in my opinion. PSR-1 is just a convention. We cannot resolve = name conflicts in the core based on this. If we want to go that way, = let's display an E_STRICT message when encountering an all-lowercase = class name, but that's another debate and I don't think anyone is = willing to enforce PSR rules in the core. Regards Fran=C3=A7ois