Re: Again: Asymmetric Visibility and Accessor syntax
| From: | Larry Garfield | Date: | Sun, 18 Sep 2022 13:11:50 +0000 |
| Subject: | Re: Again: Asymmetric Visibility and Accessor syntax | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-118651@lists.php.net to get a copy of this message | ||
On Sun, Sep 18, 2022, at 3:00 AM, Karoly Negyesi wrote:
>> We are therefore going to proceed with
public private(set),
>> the same
> syntax as Swift and the current RFC text use.
>
> It seems my previous email went to /dev/null.
>
> This is incomprehensible.
>
> Go with public(get) private(set) please.
>
> "public private" makes no sense.
The Swift-style syntax should be read as "public visibility for all operations unless otherwise
specified, and then specify private for set". Should some other operation be broken off as
individually controllable in the future, the syntax will expand to support it without further
complication.
--Larry Garfield