Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114804
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\))
In-Reply-To: <7a40dd68-6e44-4b2a-83e2-956fe00c9e6e@www.fastmail.com>
Date: Thu, 10 Jun 2021 00:08:02 -0400
Cc: php internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <81EDBC9A-D6C7-451A-8B77-7EE61D1580A5@newclarity.net>
References: <CAF+90c-W_g9Mt9yMNzBWfMEmQP287a7A6S75RyZo2fvUO2uGXQ@mail.gmail.com>
 <CAEZPtU61cfg4thuHOWOcpVFQo7pjZzgHr3QckiYqC9i=U6exOA@mail.gmail.com>
 <7a40dd68-6e44-4b2a-83e2-956fe00c9e6e@www.fastmail.com>
To: Larry Garfield <larry@garfieldtech.com>,
 Nikita Popov <nikita.ppv@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Readonly properties
From: mike@newclarity.net (Mike Schinkel)

Hi Larry,

Thanks for the response.

> On Jun 9, 2021, at 12:51 PM, Larry Garfield <larry@garfieldtech.com> =
wrote:
>=20
> Pierre and Mike:
>=20
> "Asymmetric visibility" as we keep referring to it would mean the =
"implicit accessors only" version of this: =
https://wiki.php.net/rfc/property_accessors
>=20
> That is, it would let you define public/private/protected for get and =
set operations on a property separately from each other.
>=20
> There are three key differences between readonly and asymmetric =
visibility as described there:
>=20
> * Asymmetric visibility would allow a property to be reassigned =
multiple times from within a class, readonly would allow writing to it =
only once when it's uninitialized.  Whether one of those is too-tight or =
too-loose is a matter of opinion and context.

When I read your statement I first thought you were wrong, but then I =
re-read Nikitia's RFC[1] and realized that RFC stated the properties of =
an object assigned to a readonly property *could* be updated, but *not* =
the readonly property itself.

I wonder if I was the only one who read that mistakenly?

Anyway, have either you or Nikita considered making a distinction =
between 'public readonly' and 'private readonly' such that one could =
disallow any changes after initialization and the other could allow =
changes but only within the class?

-Mike
[1] https://wiki.php.net/rfc/readonly_properties_v2#proposal=