Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110794
MIME-Version: 1.0
References: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
 <49219ad7-124f-6b95-b691-984c69f8a1d8@freedom.nl>
In-Reply-To: <49219ad7-124f-6b95-b691-984c69f8a1d8@freedom.nl>
Date: Tue, 30 Jun 2020 14:46:43 +0200
Message-ID: <CAHRtwKZeA_4LOq+efQGAkbwZA9QwU+eK3RcSSSvV-3MSbVNVZg@mail.gmail.com>
To: Dik Takken <d.h.j.takken@freedom.nl>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e7c8e405a94c9130"
Subject: Re: [PHP-DEV] [RFC] Property write visibility
From: andre.romcke@gmail.com (=?UTF-8?B?QW5kcsOpIFLDuG1ja2U=?=)

--000000000000e7c8e405a94c9130
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> Perhaps another option could be to use attributes:
>
>  <<ReadOnly>>
>  public int $id;


I=E2=80=99d actually also like a syntax like that as well for ReadOnly and
Immutable in the end.
It's more readable and it would be possible to annotate on the class level
as well (to affect all properties).

So I initially explored* in this direction, however if we go that way first
we'll likely end up with any reflection code
having to deal with attributes and understand their underlying visibility
semantics.

If we rather go this route of first introducing the concept of disconnected
visibility. The reflection API is
far clearer / understandable, more future proof, and adding the attributes
as immediate syntax sugar
followup is far more straightforward.

* initial explorative draft rfc:
https://wiki.php.net/rfc/readonly_and_immutable_properties

--000000000000e7c8e405a94c9130--