Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110769
MIME-Version: 1.0
References: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
In-Reply-To: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
Date: Mon, 29 Jun 2020 13:00:48 +0300
Message-ID: <CAGgaK7LP5foae=zV7gKPhax4Sgp1D6BtQwPmwbe3CpPjpwqi+A@mail.gmail.com>
To: =?UTF-8?B?QW5kcsOpIFLDuG1ja2U=?= <andre.romcke@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b6527105a936224c"
Subject: Re: [PHP-DEV] [RFC] Property write visibility
From: maxsem.wiki@gmail.com (Max Semenik)

--000000000000b6527105a936224c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 29, 2020 at 12:42 PM Andr=C3=A9 R=C3=B8mcke <andre.romcke@gmail=
.com>
wrote:

> This enables readonly, write-only and immutable like semantics for PHP's
> properties.
>

I agree that there is a use case for it, however I don't think the proposed
syntax `public:private` is intuitive. Maybe we can come up with something
better?


--=20
Best regards,
Max Semenik

--000000000000b6527105a936224c--