Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56419
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zerocue.com designates 74.115.204.80 as permitted sender)
To: "internals@lists.php.net" <internals@lists.php.net>
Thread-Topic: Multiple Visibility Level Getters/Setters
Thread-Index: AcymXJz+NJwQSDzSQRSE1F1zSCB5GA==
Date: Sat, 19 Nov 2011 01:46:09 +0000
Message-ID: <9570D903A3BECE4092E924C2985CE48539811627@MBX206.domain.local>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_9570D903A3BECE4092E924C2985CE48539811627MBX206domainloc_"
MIME-Version: 1.0
Subject: Multiple Visibility Level Getters/Setters
From: cpriest@zerocue.com (Clint M Priest)

--_000_9570D903A3BECE4092E924C2985CE48539811627MBX206domainloc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

What would everyone think about multiple levels of visibility for getters/s=
etters?

class Sample {

public $Variable {
                public get { return "Public"; }
                protected get { return "Protected"; }
                private get { return "Private"; }

                public set { ... }
                private set { ... }
}
}

Whichever getter/setter would be called with the most restricted access, so=
 externally public, internally protected (if inherited) or private from wit=
hin.

Any value to this?  I can see some use cases and wouldn't be any more diffi=
cult to implement into what I'm already doing.

-Clint

--_000_9570D903A3BECE4092E924C2985CE48539811627MBX206domainloc_--