Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:40473 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60614 invoked from network); 11 Sep 2008 17:45:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Sep 2008 17:45:25 -0000 Authentication-Results: pb1.pair.com header.from=sv_forums@fmethod.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=sv_forums@fmethod.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fmethod.com from 69.16.228.148 cause and error) X-PHP-List-Original-Sender: sv_forums@fmethod.com X-Host-Fingerprint: 69.16.228.148 unknown Linux 2.4/2.6 Received: from [69.16.228.148] ([69.16.228.148:54988] helo=host.fmethod.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 56/93-42936-43959C84 for ; Thu, 11 Sep 2008 13:45:25 -0400 Received: from [83.228.56.37] (port=1475 helo=pc) by host.fmethod.com with esmtpa (Exim 4.69) (envelope-from ) id 1KdqEL-0006QV-9j; Thu, 11 Sep 2008 12:45:21 -0500 Message-ID: <62D4E81A9E5247379E45F18BFEC7D3FF@pc> To: "Greg Beaver" Cc: References: <48C94F10.1000508@chiaraquartet.net> Date: Thu, 11 Sep 2008 20:45:12 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="windows-1251"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.fmethod.com X-AntiAbuse: Original Domain - lists.php.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - fmethod.com Subject: Re: [PHP-DEV] Re: Scoping of "use" statements and a strategy for 5.3/6.0 release of namespace From: sv_forums@fmethod.com ("Stan Vassilev | FM") > Stan Vassilev | FM wrote: >> Hi, >> >> Multiple namespaces per file were introduced to allow certain >> workflows in PEAR and frameworks like Symphony which can combine >> multiple classes and namespaces in a single package. >> >> They work like this: >> >> >> namespace X; >> >> ... >> >> namespace Y; >> >> ... >> >> >> The problem is, no one thought of scoping "use" statements, so now >> those merged files share their "use" imports, thus breaking all the >> code where collisions occur. > > Hi, > > Stan, did you actually try this out? According to my checkout of CVS, > you're wrong. Try this script: > What's the logic behind namespace declaration affecting file-level import statements. Looks like such a hack to me.