Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41566 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29855 invoked from network); 30 Oct 2008 00:46:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Oct 2008 00:46:12 -0000 Authentication-Results: pb1.pair.com header.from=helly@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=helly@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender) X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 85.214.94.56 aixcept.net Linux 2.6 Received: from [85.214.94.56] ([85.214.94.56:35489] helo=h1149922.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D0/CB-58116-2D309094 for ; Wed, 29 Oct 2008 19:46:12 -0500 Received: from MBOERGER-ZRH.corp.google.com (145-124.106-92.cust.bluewin.ch [92.106.124.145]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by h1149922.serverkompetenz.net (Postfix) with ESMTP id 7F00E11F158; Thu, 30 Oct 2008 01:46:07 +0100 (CET) Date: Thu, 30 Oct 2008 01:43:17 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1192158774.20081030014317@marcus-boerger.de> To: Ron Rademaker CC: internals@lists.php.net In-Reply-To: <49081AEE.3000604@virtualbuilding.nl> References: <49081AEE.3000604@virtualbuilding.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Class visibility in namespaces From: helly@php.net (Marcus Boerger) Hello Ron, we agreed long ago on a very easy scheme, there shall only be is-a and public classes. marcus Wednesday, October 29, 2008, 9:12:30 AM, you wrote: > 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 Best regards, Marcus