Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41546
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain virtualbuilding.nl from 81.4.92.194 cause and error)
Message-ID: <49081AEE.3000604@virtualbuilding.nl>
Date: Wed, 29 Oct 2008 09:12:30 +0100
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Class visibility in namespaces
From: r.rademaker@virtualbuilding.nl (Ron Rademaker)

Hi,

I'm hoping I don't cause yet another flame war about the n-word ;)

I was wondering if namespaces are going to support class visibility, and 
if no, would it be worth considering adding that feature? What I mean 
exacty is:

In namespace Foo:

public class Foo { }

protected class Bar { }

- Bar can be instantiated from any class (or function) within the 
namespace Foo

Outside of namespace Foo:

- class Foo in namespace Foo can be instantiated
- class Bar in namespace Foo can't be instantiated

Ron