Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79947 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45028 invoked from network); 25 Dec 2014 21:58:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Dec 2014 21:58:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.175 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.214.175 mail-ob0-f175.google.com Received: from [209.85.214.175] ([209.85.214.175:48230] helo=mail-ob0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EE/32-31774-3988C945 for ; Thu, 25 Dec 2014 16:58:44 -0500 Received: by mail-ob0-f175.google.com with SMTP id wp4so32868298obc.6 for ; Thu, 25 Dec 2014 13:58:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=zDMeAoqBg7fwG6BjxG/B+K2F5RP+bFrQw2J57Z3EGVY=; b=Lsv2ibR9JOp1Hib8YMqGhNBrlQSX02m1d/8wMYX+qX1mUqkZ75WQQXC8PalD7x5DyJ RgXix4CYeDMmWrRD5NfJO7UobUUA0NtWOJNIm4gYSyea2Po3LPQxqMDAdq5FXP0DRAL4 b7+AzSULUmHG8OjNYMCSTA2t6WlVKwdF1hUIt4WKnbzNDepwpH2ubo+j+5JYJRIaFrp4 uJigSQX5a6PW6JR1qmVvRCofPVVAKmPBs+YbvdmH6Hy7jtqzrwGFgD0FiFh5SFrdcQlA CoDbjMlpmv8TpboNkAqYaPzHk82jXSeTUBKrf8J7+Gc2X3eghYvEujz+MyPxiySjnvAf aaXg== X-Received: by 10.182.27.207 with SMTP id v15mr23582889obg.21.1419544721188; Thu, 25 Dec 2014 13:58:41 -0800 (PST) Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id xs2sm12559536obc.7.2014.12.25.13.58.39 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Dec 2014 13:58:40 -0800 (PST) Message-ID: <549C888E.8020104@gmail.com> Date: Thu, 25 Dec 2014 13:58:38 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Pierre Joye , Nikita Popov CC: Yasuo Ohgaki , Ferenc Kovacs , PHP Internals , Alain Williams , Guilherme Blanco , David Muir , Andrea Faulds , Xinchen Hui , Kevin Israel , Mike Dugan , francois@tekwire.net References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr> <000d01d01ec2$46f2f280$d4d8d780$@yahoo.fr> <009a01d01ff4$7d145470$773cfd50$@tekwire.net> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols From: smalyshev@gmail.com (Stanislav Malyshev) 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. -- Stas Malyshev smalyshev@gmail.com