Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32225
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.187 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=sKAwsagOx6WmRcvwp64D9rYqAD4EX9dAaCFsWzK8ILEz5QlAyfuli2HZtJd0AxITbfzWRr2cPzJNZkuaZ5bYw4p44iE3sqa1Ze/pWzOljRz0OvuZzpml+nJdnVVHgBntuN7eG+WPu3U7NsiS/ilpczZjTRB2Hi+nlCi67bn8kYk=
Message-ID: <b5f7bf6c0709101658l457c86cke064f9949f5cedaf@mail.gmail.com>
Date: Mon, 10 Sep 2007 19:58:39 -0400
Sender: david.coallier@gmail.com
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "PHP Internals" <internals@lists.php.net>
In-Reply-To: <46E5D567.8090205@zend.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46E5D163.4050800@zend.com>
	 <b5f7bf6c0709101628t24f070e3y194e6bf65f318a21@mail.gmail.com>
	 <46E5D567.8090205@zend.com>
Subject: Re: [PHP-DEV] multiple namespace per file
From: davidc@php.net ("David Coallier")

On 9/10/07, Stanislav Malyshev <stas@zend.com> wrote:
> > Ok, I was wondering to myself, do you guys think it would be possible
> > to do something like having an endnamespaces; keyword that would put
> > an end to the namespace definition?
>
> Oh no :) It doesn't look good and it doesn't solve the problem. Hint:
> the braces have the same problem (that's why I asked not to suggest them
> :) since the problem is per-file imports vs. multiple global spaces. I
> can explain more if you wish but basically it's not about finding the
> right delimiter, it's about making something that would work when files
> are combined together (repeatedly). If you allow global space there, it
> starts to look and work seriously weird.
> --

Yeah you are right, I also thought it looked extremely ugly.

I have thought of a few things (since I am the combined/aggregated
files advocate) and I actually think that this approach (Having
multiple namespace per file like you mentionned) would work pretty
well. After taking a look at this problem from another point of view,
I realized that if we can manage to make the multiple namespace per
file as you mentionned earlier then it would be rather trivial.

I like the implementation you suggested earlier, you got +1 from me ;-)



More question, just like this,

when you do:

<?php

namespace A;
require 'somefile.php';
class AX{}

namespace B;
class BX{ }

?>

is somefile.php also included in the B namespace since you cannot
include it in global scope.



Next step ? Renaming to packages ? :P (No please dont anyone it's just a joke)


> Stanislav Malyshev, Zend Software Architect
> stas@zend.com   http://www.zend.com/
> (408)253-8829   MSN: stas@zend.com
>
>


Thanks,



-- 
David Coallier,
Founder & Software Architect,
Agora Production (http://agoraproduction.com)
51.42.06.70.18