Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97101
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 185.153.204.204 cause and error)
To: internals@lists.php.net
References: <CAA69SC4th-Hkxj162xn3RWAG44tFkhGTo3Pm=mephPdSHfcHsw@mail.gmail.com>
 <CADqTB_jPm6BB78wCbvNVj0gzGUy=M6tdPhB0dH34U+AXZQgiDA@mail.gmail.com>
 <30416a57-2cb5-d192-9b3d-1546a11d9661@rochette.cc>
Message-ID: <e16632dc-0714-5b5a-3136-2c38df385af1@lsces.co.uk>
Date: Mon, 21 Nov 2016 09:20:20 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <30416a57-2cb5-d192-9b3d-1546a11d9661@rochette.cc>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Immutability RFC
From: lester@lsces.co.uk (Lester Caine)

On 21/11/16 08:46, Mathieu Rochette wrote:
>> The term 'immutable", especially for the property-annotation, doesn't
>> strictly seem correct to me either, as for example, I can annotate a
>> public
>> property as immutable, but if I put an object in there, that object is
>> not
>> necessarily immutable. The correct term for this feature, especially for
>> properties, I would think is "readonly" - which would be consistent with
>> the description of certain existing properties in PHP APIs, such as
>> PDOStatement::$queryString, as well as with other languages such as C#.

> I'm not sure about that one because I can't find it explicitly in the
> rfc (maybe it need to be added ?) but I think immutable properties only
> accept immutable scalar or objects. otherwise you're right, it would not
> be immutable

The RFC is yet another attempt to add rules to areas of PHP without
getting back to the very basic ... variables are the base element that
in an ideal world would have a full set of properties. type, range/enum,
size, read-only and the like. A sub set of properties on an object may
need to be read-only and if that includes the values returned by the
methods of the object then the object itself becomes read-only. Current
options for doing this include things like 'getters' and 'setters' and
other standards applied in user land including PHP-FIG, but there still
seems not incentive to address the basic building block and make it work
the same way for everybody whether simply validating raw data, or
protecting fields that have rules preventing updating.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk