That would be a resounding no from everyone. :)
-Original Message-
From: Hannes Magnusson [mailto:hannes.magnus...@gmail.com]
Sent: Friday, November 18, 2011 8:16 PM
To: Clint M Priest
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Multiple Visibility Level Getters/Setters
On Sat
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 wrote:
> Just throw an error if conflicting accessors
Just throw an error if conflicting accessors are defined. In the case of
subtypes: accessors may broaden the interface, but not limit it => LSP. So it’s
fine to make a parents protected accessor public, but not the other way around.
Am 19.11.2011 um 02:46 schrieb Clint M Priest:
> What would ev
On Sat, Nov 19, 2011 at 02:46, Clint M Priest wrote:
> What would everyone think about multiple levels of visibility for
> getters/setters?
>
> class Sample {
>
> public $Variable {
> public get { return "Public"; }
> protected get { return "Protected"; }
>
