Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79889
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.176 as permitted sender)
Message-ID: <5499B598.8070000@gmail.com>
Date: Tue, 23 Dec 2014 10:34:00 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Robert Stoll <php@tutteli.ch>, 'Leigh' <leight@gmail.com>, 
 guilhermeblanco@gmail.com
CC: 'PHP internals' <internals@lists.php.net>
References: <CAFp73XvChnyz3LH3=t4zyww+TjpG_XUzq0+1-ygNFP-xApDgfw@mail.gmail.com> <CAPwsocEEoK92S-T3_od10k4Z5f+x895YA0JrOzhwZGBubaGPiw@mail.gmail.com> <001e01d01e97$143188f0$3c949ad0$@tutteli.ch>
In-Reply-To: <001e01d01e97$143188f0$3c949ad0$@tutteli.ch>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: AW: [PHP-DEV] [RFC] Package private class
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> 
> namespace ch.tutteli.foo{ public for ch.tutteli.bar, ch.tsphp* 
> private class Foo{} }

This looks like a recipe for totally unmaintainable situation, where
each class has its own list of places where it is visible, and the lists
are different for each class. I can kind of get when the people want a
class that is not visible to other code. But if it's not the situation,
just use regular class.

I don't think PHP needs arcane rules of class visibility that will be
used by 0.001% of users and even those would probably use it wrong since
there's no way to keep all those individual lists in sync.

-- 
Stas Malyshev
smalyshev@gmail.com