Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89024
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.43 as permitted sender)
MIME-Version: 1.0
Date: Sun, 1 Nov 2015 17:04:24 +0100
Message-ID: <CACjyb+z3Aenebqe4Q5_=VP2Wbs31KwTZhs_Ts-PAHDDraGoALQ@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1144360245963d05237cd2d5
Subject: Friend class/function
From: geolim4@gmail.com (georges)

--001a1144360245963d05237cd2d5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=E2=80=8BHi php internals,

I recently discovered =E2=80=8Bthe "friendship concept" in c++ and i really=
 love
the concept.
And i wonder if the php internals would be interested to implements it in
the next 7.x major version.


=E2=80=8BThe concept is simple:

It would allow declared "friend"=E2=80=8Bclass method/function to call a
private/protected member of an other class:


The syntax could be like this (for a single friendship):

private function extractDataFromCache() friend myFriendClass1
{

}


or like this for many friendships:

private function extractDataFromCache() friend
{myFriendClass1::method1, myFriendClass2::method1,
myFriendClass3::method1}
{

}


In this way extractDataFromCache() could be called directly by method1 in
myFriendClass1 and myFriendClass2 etc....

Off course deep calling should not be allowed. (E.g a function inside
myFriendClass1 that will call extractDataFromCache() won't inherit the
friendship.

Regards,
Georges

--001a1144360245963d05237cd2d5--