Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63549
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
MIME-Version: 1.0
Sender: amaury.bouchard@gmail.com
In-Reply-To: <9570D903A3BECE4092E924C2985CE485612C2595@MBX214.domain.local>
References: <9570D903A3BECE4092E924C2985CE485612C2595@MBX214.domain.local>
Date: Sat, 20 Oct 2012 09:29:49 +0200
Message-ID: <CAPaKmRmghPKO-4wTFXVTpiUeb8mY34B799PgTLmiTtx3fw-ZkQ@mail.gmail.com>
To: Clint Priest <cpriest@zerocue.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf303a360b23881304cc789704
Subject: Re: [PHP-DEV] [RFC] Accessors : read-only / write-only keywords
From: amaury@amaury.net (Amaury Bouchard)

--20cf303a360b23881304cc789704
Content-Type: text/plain; charset=ISO-8859-1

  read-only => final set null;
It begins to be verbose.

As I said many times, why don't you want to use the "const" keyword? It
already exists and is pretty well understood by everybody.



2012/10/20 Clint Priest <cpriest@zerocue.com>

> 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?
>
> -Clint
>
>
>

--20cf303a360b23881304cc789704--