Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32220
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.114 as permitted sender)
Message-ID: <46E5D163.4050800@zend.com>
Date: Mon, 10 Sep 2007 16:21:07 -0700
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 'PHP Internals' <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: multiple namespace per file
From: stas@zend.com (Stanislav Malyshev)

Hi!

Following the feedback from the community, we (mostly me and Dmitry) 
tried to find a good model that would allow multiple namespaces per file 
without running into too many problems and complications, and would 
allow to bundle multiple namespaced files together without 
modifications. It looks like it is possible to do, but only under the 
following condition: the file can have multiple namespaces, but if the 
file has namespaces, then it can have no code outside namespaces.

For example, this would work:
namespace A;
class X {}
namespace B;
class Y {}

This would not work:
class X {}
namespace A;
class Y {}

This would not work either:
require 'foo/bar.php';
namespace A;
class X {}

This however would work:
namespace A;
require 'foo/bar.php';
class X {}
namespace B;
class Y {}

So, for the people that wanted multiple NS per file, would such solution 
work?

P.S. this is *not* a "should we use braces" thread, so please don't :)
-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com