Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79951 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53442 invoked from network); 25 Dec 2014 23:33:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Dec 2014 23:33:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.169 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.216.169 mail-qc0-f169.google.com Received: from [209.85.216.169] ([209.85.216.169:47108] helo=mail-qc0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 23/B3-31774-CDE9C945 for ; Thu, 25 Dec 2014 18:33:48 -0500 Received: by mail-qc0-f169.google.com with SMTP id w7so6942361qcr.28 for ; Thu, 25 Dec 2014 15:33:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9I6UhqYI9oq71pSBQ5Tvq7EUA+6cPeDdAGPHV5BZb6A=; b=yz17DHhOPmFrlbogVq/GMs+jmIoLfnsgPmlLDV+SBP92dwo+gDihDdTP0p0fTGolkx oxOJlajuXMP8wC0z+C76/vMt3PgDpdapruglYQlZjuzJ00/NKzNbTyhyDw78N9e2iiRz lgCKnuP/9ZW/EsJ2SVrLg5fBiBWaO+439D82uAYpshpnsHCg1/cuBLuwfz8cCUvL6fp8 jRqSSw4Zq06NsK55fzd9+h69xqGAZYWt+kDG/Azas8I10dkdRfX8/07BnnybZBdlMDqN BKuuJxPvL/Nj7uLdcdh5nZSef5XF2ljieTCsNJJHfzWmMvgaf7oErJGR28W0O8JnHHyc qBWA== MIME-Version: 1.0 X-Received: by 10.224.54.2 with SMTP id o2mr64846463qag.63.1419550425600; Thu, 25 Dec 2014 15:33:45 -0800 (PST) Received: by 10.140.22.106 with HTTP; Thu, 25 Dec 2014 15:33:44 -0800 (PST) Received: by 10.140.22.106 with HTTP; Thu, 25 Dec 2014 15:33:44 -0800 (PST) In-Reply-To: <549C888E.8020104@gmail.com> References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr> <000d01d01ec2$46f2f280$d4d8d780$@yahoo.fr> <009a01d01ff4$7d145470$773cfd50$@tekwire.net> <549C888E.8020104@gmail.com> Date: Fri, 26 Dec 2014 10:33:44 +1100 Message-ID: To: Stas Malyshev Cc: Ferenc Kovacs , Yasuo Ohgaki , PHP Internals , Alain Williams , Guilherme Blanco , Nikita Popov , David Muir , Xinchen Hui , Andrea Faulds , Kevin Israel , francois@tekwire.net, Mike Dugan Content-Type: multipart/alternative; boundary=001a1132f080dbd75b050b12d6f4 Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols From: pierre.php@gmail.com (Pierre Joye) --001a1132f080dbd75b050b12d6f4 Content-Type: text/plain; charset=UTF-8 On Dec 26, 2014 4:58 AM, "Stanislav Malyshev" wrote: > > Hi! > > > At the very least that sounds like a less intrusive step, as methods and > > classes are usually already written "correctly". > > To me, it sounds like needless nuisance - the code works, but wastes > time to produce warnings that nobody reads. If your have a code that > relies on autoloaders and case mix breaks it, your autoloading code can > take care of it and produce whatever handling you need (from log > messages up to bailing out). But if you have the code that uses mixed > case and it works for you, these warnings would do nothing - they'd just > be ignored and we'd hurt performance and achieve nothing. My point too. I was only referring to the options for the RFC. --001a1132f080dbd75b050b12d6f4--