Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79832 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35423 invoked from network); 21 Dec 2014 00:31:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Dec 2014 00:31:16 -0000 Authentication-Results: pb1.pair.com header.from=francois@tekwire.net; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=francois@tekwire.net; spf=softfail; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain tekwire.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@tekwire.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:10218] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D1/80-32072-2D416945 for ; Sat, 20 Dec 2014 19:31:15 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 719DA4B008E; Sun, 21 Dec 2014 01:30:04 +0100 (CET) Reply-To: To: "'Andrea Faulds'" Cc: References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr> In-Reply-To: Date: Sun, 21 Dec 2014 01:31:09 +0100 Message-ID: <002f01d01cb5$6b4ad8f0$41e08ad0$@tekwire.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: AQHy2TXkJ8WGpUhO4XSbKZAIVj0P4QEp/7CMnEphNOA= Content-Language: fr X-Antivirus: avast! (VPS 141220-1, 20/12/2014), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols From: francois@tekwire.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) > De : Andrea Faulds [mailto:ajf@ajf.me] > I=E2=80=99d thought of doing this before, but the = backwards-compatibility cost is too > high. It is a BC break, I agree, but would the impact on PHP community be so = high ? I have never seen any PHP code which would rely on function/class = names case-insensitivity. I tested this with Automap, a map-based = autoloader, modified to work in a case-sensitive manner. I tested most = PHP frameworks and libraries and none of them had case mismatches. There = are some, probably, but I guess that most, if not all, are undetected = typos. Can't we consider such a mismatch as a bug ? That's what any = normal programmer would think, IMHO. So, I think that such a BC break on = a problematic syntax is acceptable, and would even help clean some PHP = code. What we can do to minimize the BC break, in the spirit of the migration = path discussed these last days, is to introduce an E_STRICT warning in = version 5.7, which would help programmers prepare their code for PHP 7. Regards Fran=C3=A7ois =20