Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56435
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <79A6C298-1475-4B69-A47D-27D3DEA4BC0E@strojny.net>
References: <9570D903A3BECE4092E924C2985CE48539811627@MBX206.domain.local> <79A6C298-1475-4B69-A47D-27D3DEA4BC0E@strojny.net>
Date: Sat, 19 Nov 2011 21:12:19 +0000
Message-ID: <CAF=va1WKo86JAyc2k9GuOgMozBD3HsZyxv4mxe5_p_btKoZZFw@mail.gmail.com>
To: Lars Strojny <lars@strojny.net>
Cc: Clint M Priest <cpriest@zerocue.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec51d2a38ea679f04b21ce9cd
Subject: Re: [PHP-DEV] Multiple Visibility Level Getters/Setters
From: ava3ar@gmail.com (Keloran)

--bcaec51d2a38ea679f04b21ce9cd
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

personally i think only public should be done with this method

all others should be follow the __set/__get method, since if you need
special rules, then they would be set-able by a public method

On Sat, Nov 19, 2011 at 7:45 PM, Lars Strojny <lars@strojny.net> wrote:

> Just throw an error if conflicting accessors are defined. In the case of
> subtypes: accessors may broaden the interface, but not limit it =3D> LSP.=
 So
> it=92s fine to make a parents protected accessor public, but not the othe=
r
> way around.
>
> Am 19.11.2011 um 02:46 schrieb Clint M Priest:
>
> > What would everyone think about multiple levels of visibility for
> getters/setters?
> >
> > 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
> within.
> >
> > Any value to this?  I can see some use cases and wouldn't be any more
> difficult to implement into what I'm already doing.
> >
> > -Clint
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--bcaec51d2a38ea679f04b21ce9cd--