Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89737
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain free.fr from 212.27.42.2 cause and error)
Date: Tue, 8 Dec 2015 12:01:34 +0100 (CET)
To: Dustin Wheeler <mdwheele@ncsu.edu>
Cc: internals@lists.php.net
Message-ID: <348752699.466407212.1449572494594.JavaMail.root@zimbra71-e12.priv.proxad.net>
In-Reply-To: <CADMz3wfdBdzcNjcNHRQetRNTpDpsrCoQ4_XikRCCbwy+10CxTw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Class Friendship in PHP
From: flaupretre@free.fr
References: <CADMz3wfdBdzcNjcNHRQetRNTpDpsrCoQ4_XikRCCbwy+10CxTw@mail.gmail.com>

Hi,

Thanks  for this interesting and well-documented message.

When looking at the history about class friendship, you may have seen that =
the concept was globally rejected in favor of Guilherme's project of 'packa=
ge-privacy'. I personnally think friend classes are a different and more po=
werful concept and, if you feel strong enough to write and defend an RFC an=
d defend it, I encourage you to go on.

These are details:

- I would prefer providing the same access to friend classes as parents and=
 descendants : that is allow 'protected' but keep private reserved to the c=
lass. This way, when looking at the class code, you know that private data =
cannot be accessed, even by friends.

- I would extend the syntax to namespaces. For examples, '\MyNS\' (syntax t=
o dicuss) would declare every class in the '\MyNS' namespaces or sub-namesp=
aces as friends. Must support 'friend __NAMESPACE__' or something equivalen=
t. This, coupled with a protected __construct() method would provide someth=
ing quite similar to package-private access, but more extensible and powerf=
ul.

Regards

Fran=C3=A7ois