Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17417
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <52.32.58254.87AA6E24@pb1.pair.com>
To: internals@lists.php.net
References: <52.31.61486.E8DCDD24@pb1.pair.com><1122328113.647.16.camel@boost.home.ahk><538910800.20050725235918@marcus-boerger.de> <1122412467.4938.7.camel@boost.home.ahk>
Date: Tue, 26 Jul 2005 17:26:21 -0400
Lines: 33
Subject: Re: [PHP-DEV] [PATCH] Namespace Patch, Alpha 3
From: jrhernandez05@gmail.com ("Jessie Hernandez")

Hello Alex,

"Alex Kiesel" <alex@kiesel.name> wrote in message
news:1122412467.4938.7.camel@boost.home.ahk...
>
> import $this is just something I'd expect PHP to be able to deal with -
> but I could live without it.
>

I never meant to implement this, and I also agree with Marcus that there's
no reason to allow it.

> Btw, if you're saying "Namespaces are for spreading/controlling
> responsibilities", do you mean something like the package access level
> for methods and member variables Java has? Is anyone thinking of
> introducing this?
>

Could you please clarify what you're referring to here? If you are talking
about "package scope" for classes, this is already present in my patch. When
inside a namespace, if you declare a class as "private class my_class", then
that class will only be accessible from that namespace (even if the classes
are spread out in several files, as long as they're in the same namespace,
those classes can use the private class). Right now, I'm enforcing this by
checking that the classes are both in the same directory. Once I finish my
__autoload change, I'll have to instead check the namespace "prefixes" on
both class names to allow flexibility.


--
Jessie