Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41167 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 69503 invoked from network); 16 Oct 2008 20:50:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Oct 2008 20:50:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.163 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 212.25.124.163 il-gw1.zend.com Windows 2000 SP4, XP SP1 Received: from [212.25.124.163] ([212.25.124.163:3830] helo=il-gw1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 30/B2-12818-F29A7F84 for ; Thu, 16 Oct 2008 16:50:57 -0400 Received: from us-ex1.zend.com ([192.168.16.5]) by il-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 16 Oct 2008 22:51:14 +0200 Received: from [192.168.16.110] ([192.168.16.110]) by us-ex1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 16 Oct 2008 13:50:44 -0700 Message-ID: <48F7A924.4000304@zend.com> Date: Thu, 16 Oct 2008 13:50:44 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Greg Beaver CC: Lester Caine , PHP internals References: <48F6B3C5.9030102@chiaraquartet.net> <7f3ed2c30810152312h5391b25dke2695362c8d28d3b@mail.gmail.com> <48F6E50E.4010107@lsces.co.uk> <48F75BA3.30603@zend.com> <48F77416.3010106@chiaraquartet.net> <48F77938.1020206@zend.com> <48F7A5BF.5090308@chiaraquartet.net> In-Reply-To: <48F7A5BF.5090308@chiaraquartet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 Oct 2008 20:50:44.0926 (UTC) FILETIME=[DC1B75E0:01C92FD0] Subject: Re: [PHP-DEV] namespaces sanity: addition to RFC explaining why Stas'sproposal doesn't work From: stas@zend.com (Stanislav Malyshev) Hi! >>> >> Classname::Method(); >>> ?> >>> >>> The proposal does not solve the name conflict. If no one rewrites their >> Right, it does not. So doesn't yours - you need to modify the code in >> both cases. > the solution I proposed emits an E_WARNING on the conflict. You proposed a number of solutions, apparently. That's why I asked to restrict the number of variants - even people who watch the discussion can't be sure what we are talking about now. Do you propose to _always_ throw E_WARNING even if there was no actual conflict? Then I am against it - in 99.9% of the code this warning would be useless and would only annoy people. If you propose to throw warning only if actual conflict exists - the question stays how do you know it exists. -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com