Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78948
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.208 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <CAFp73Xu9yq6qLaYUO57CHj4=1g=naxQceNV4fNMca73e6WjpJw@mail.gmail.com>
Date: Tue, 18 Nov 2014 17:58:40 +0000
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <A67B5C10-D038-41BC-A54D-7A588B09FE49@ajf.me>
References: <CAFp73Xu9yq6qLaYUO57CHj4=1g=naxQceNV4fNMca73e6WjpJw@mail.gmail.com>
To: "guilhermeblanco@gmail.com" <guilhermeblanco@gmail.com>
Subject: Re: [PHP-DEV] [IDEA] Class modifiers support expansion
From: ajf@ajf.me (Andrea Faulds)


> On 18 Nov 2014, at 17:33, guilhermeblanco@gmail.com wrote:
>=20
> Library developers sometimes plan for extensibility of their code, but =
not
> all pieces are able to be extended and unexpected usage can lead to
> unpredictable behavior.
> Based on that, I consider it may be a good addition to PHP to add =
class
> visibility support and enhance existing modifiers' support.

I was thinking the very same thing after __construct() came up, but =
wasn=E2=80=99t sure how it should work. :)

> Now what I mean by class visibility, it requires a better discussion =
on how
> it could behave, since any other language relies on nested classes to
> expose this support. Nevertheless, PHP's lack of Open/Close principle
> support could be addressed easily. This is my POV on how it could =
behave:
>=20
> - private classes: Can only be extended and instantiated inside of the =
same
> namespace it sits. This is the similar to private-package support in =
Java.
> - protected classes: I can't determine any similarity to any other =
language
> in this one, but it could behave somehow like: can be extended and
> instantiated anywhere within the root namespace.
> - public classes: same as current PHP support
>=20
> What do you think about it?

I think it=E2=80=99s a good idea, the problem is defining private and =
protected.

I wonder if this is something autoloaders could handle? private classes =
might be visible only within the same file, while protected classes =
might be visible only to other files the autoloader can see.

--
Andrea Faulds
http://ajf.me/