Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118362
Date: Sun, 07 Aug 2022 11:34:04 +0100
To: internals@lists.php.net
User-Agent: K-9 Mail for Android
In-Reply-To: <CAKxcST_Mu3qDKKLgtsBBVAm=6mLirhjZ-88f+jjWeNhWyzO16A@mail.gmail.com>
References: <ec4bc6e5-39ac-4a36-9d63-cca8dc6a29a6@www.fastmail.com> <CABdc3WqQ-kLTa3C=61_=yW-yJZuP2p_QW1TNe12WuHHur7aHng@mail.gmail.com> <e122e44f-550e-4089-8100-a27df9f8c9fa@www.fastmail.com> <CAKxcST_Mu3qDKKLgtsBBVAm=6mLirhjZ-88f+jjWeNhWyzO16A@mail.gmail.com>
Message-ID: <A78DA1F7-1F74-4A94-962C-0EA5979431AD@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Asymmetric visibility
From: rowan.collins@gmail.com (Rowan Tommins)

On 5 August 2022 21:04:34 BST, Paul Dragoonis <dragoonis@gmail=2Ecom> wrote=
:
>2=2E when I opened the RFC and looked at the syntax, I wasnt able to
>intuitively (self documenting code) figure out what and why was going on=
=2E
>
>3=2E The syntax is heavily implicit as to what each keyword and syntax me=
ans,
>so the general PHP developer would struggle or mis understand what is goi=
ng
>on=2E


Can you expand on where you think the ambiguity / implicitness is? As I un=
derstand it, the RFC is proposing exactly three new combined access levels:

- "public private(set)"
- "public protected(set)"
- "protected private(set)"

Although aesthetically it will take a bit of getting used to, it seems to =
me pretty clear that the first means "mostly public, but private if you wan=
t to set it", and so on=2E

The only thing I can think of that could be described as "implicit" is tha=
t accessing a property by reference is considered a "set" operation, which =
I'm not sure how any implementation could avoid=2E

Regards,

--=20
Rowan Tommins
[IMSoP]