Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63571
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5082F701.7090602@lsces.co.uk>
References: <9570D903A3BECE4092E924C2985CE4856140BA80@MBX202.domain.local> <5082F701.7090602@lsces.co.uk>
Date: Sat, 20 Oct 2012 12:34:16 -0700
Message-ID: <CA+Ky_uNYDHJr8ZsPM32+zYYVfC3ZYnN7KsseUEh+h4SrrhAptg@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=0016e6dd97b7188dec04cc82b7fd
Subject: Re: [PHP-DEV] [RFC] Accessors : read-only / write-only keywords
From: ww.galen@gmail.com (Galen Wright-Watson)

--0016e6dd97b7188dec04cc82b7fd
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Oct 20, 2012 at 12:09 PM, Lester Caine <lester@lsces.co.uk> wrote:

>
>  I am in favor of eliminating the read-only/write-only keywords and
>> implementing no "special code" to make what was read-only/write-only
>> language enforced.  I think the alternatives with final are just fine and
>> good enough and will let userland programming enforce it if they so desire.
>>
> But the question still remains. Isn't a read only variable simply a
> 'const'? Why do we need anything more than that? It explains exactly why it
> has been defined without any ambiguity and works everywhere.
>

A read-only variable may be calculated from other values, and there may not
be an inverse calculation. As a concrete example, consider an invoice total
calculated from line items. It will change as the line items change, but it
wouldn't make sense to me to be able to set the order total and have that
somehow be back-propagated to the line items.

--0016e6dd97b7188dec04cc82b7fd--