Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30908 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85656 invoked by uid 1010); 14 Jul 2007 06:59:43 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 85640 invoked from network); 14 Jul 2007 06:59:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jul 2007 06:59:43 -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 63.205.162.114 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 63.205.162.114 unknown Windows 2000 SP4, XP SP1 Received: from [63.205.162.114] ([63.205.162.114:20490] helo=us-ex1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 12/6E-11631-D5478964 for ; Sat, 14 Jul 2007 02:59:43 -0400 Received: from [127.0.0.1] ([192.168.17.11]) by us-ex1.zend.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Jul 2007 23:59:38 -0700 Message-ID: <46987455.9020208@zend.com> Date: Fri, 13 Jul 2007 23:59:33 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Markus Fischer CC: Dmitry Stogov , internals@lists.php.net References: <000501c7c247$56a551d0$6e02a8c0@thinkpad> <46986DAA.4080404@fischer.name> In-Reply-To: <46986DAA.4080404@fischer.name> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Jul 2007 06:59:39.0270 (UTC) FILETIME=[8BD73260:01C7C5E4] Subject: Re: [PHP-DEV] FW: Simple Namespace Proposal From: stas@zend.com (Stanislav Malyshev) > as only being a general lurker on this list, I remember when Namespaces > came up the first time, there were some technical problems (or just > syntactical sugar ones?) with the "::" operator also being used as a > Namespace separate additional being a class separator. > > How has this been handled or are there some caveats to watch for? There's still some ambiguity in cases like Foo::bar() but since we explicitly import namespace shortcut names we always know if there's an import name that can be substituted or class name. This means some slowdown in "hard" cases since we have to first check for import and then for class name but it's compile-time. -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com