Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63558
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <9570D903A3BECE4092E924C2985CE485612C2595@MBX214.domain.local>
References: <9570D903A3BECE4092E924C2985CE485612C2595@MBX214.domain.local>
Date: Sat, 20 Oct 2012 12:15:13 +0200
Message-ID: <CAEZPtU6o9k4A50_epcmqBnBtiYY9GuqrzTAyuCpjs4dBWUjZDQ@mail.gmail.com>
To: Clint Priest <cpriest@zerocue.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [RFC] Accessors : read-only / write-only keywords
From: pierre.php@gmail.com (Pierre Joye)

On Sat, Oct 20, 2012 at 1:07 AM, Clint Priest <cpriest@zerocue.com> wrote:
> I had thought of a deviation on some of the ideas presented to get rid of read-only/write-only while still keeping the ability to maintain their effect, if we so decide that the feature is wanted.  Here it is:
>
> class TimePeriod {
>     private $Seconds;
>
>     public $Hours {
>         get() { return $this->Hours; }
>         final set NULL;
>     }
> }
>
> It's close to what's been suggested but is pretty clear that there IS NO SETTER it could not be called within the class and since its final it cannot be over-ridden.  I've included this in the change tracking document.
>
> Thoughts?

Sorry but I don't like it, it makes me think that there is no setter
but I could set the property manually (yes, that's not an actual one
but putting myself in the shoes of a lambda user).

I actually prefer the read-only syntax, while we have to make it clear
and not confusin (see Niki's reply in this post).

Cheers,
-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org