Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79830 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30564 invoked from network); 20 Dec 2014 23:32:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Dec 2014 23:32:26 -0000 Authentication-Results: pb1.pair.com header.from=pleasestand@live.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pleasestand@live.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain live.com designates 65.55.111.109 as permitted sender) X-PHP-List-Original-Sender: pleasestand@live.com X-Host-Fingerprint: 65.55.111.109 blu004-omc2s34.hotmail.com Received: from [65.55.111.109] ([65.55.111.109:50827] helo=BLU004-OMC2S34.hotmail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6E/00-29495-90706945 for ; Sat, 20 Dec 2014 18:32:25 -0500 Received: from BLU436-SMTP36 ([65.55.111.73]) by BLU004-OMC2S34.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Sat, 20 Dec 2014 15:31:29 -0800 X-TMN: [zJ9/szriobih1pxUJ7+E1kY01frq892F] X-Originating-Email: [pleasestand@live.com] Message-ID: Date: Sat, 20 Dec 2014 18:32:17 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Paul Dragoonis , nf.laupretre@yahoo.fr CC: PHP Internals List References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr> In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 20 Dec 2014 23:31:29.0125 (UTC) FILETIME=[146B7150:01D01CAD] Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols From: pleasestand@live.com (Kevin Israel) On 12/20/2014 05:16 PM, Paul Dragoonis wrote: > It's too big of a BC change firstly. > > Secondly it has no language benefit or developer benefit. Are you sure? Autoloading schemes such as PSR-4 derive pathnames from class names without converting them to lowercase. If case mismatches go undetected and unreported, a project might work on a developer's Windows desktop (case-insensitive) yet not when uploaded to a Linux web server (case-sensitive). Or when an object instantiation or a static method call using the correct case is removed from the code, a later call using the incorrect case might break. Backward compatibility is perhaps a good reason to not make this change. However, I would like to see at least an option to report case mismatches in class names as E_STRICT errors and possibly a way to disable that for specific files or classes when necessary. > On 20 Dec 2014 22:01, "F & N Laupretre" wrote: >> I would like to propose that namespaces, functions, and classes become >> case-sensitive (constants are already case-sensitive). Actually, I never >> understood why they are case-insensitive. Even if the performance gain is >> negligible, I think it could be the right time to question this.