Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123460
Message-ID: <9ee56480-66f0-4f1a-9d4b-20a0b30e66fb@bastelstu.be>
Date: Wed, 29 May 2024 22:09:00 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Asymmetric Visibility, v2
To: Andreas Hennings <andreas@dqxtech.net>,
 Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
References: <0a6a61cd-f203-4dea-a7f8-97e6b885c52d@app.fastmail.com>
 <CAB-Bujb7MJ_+t7F1=EF5gKTgKsm44JnAUinN4nnwBf52q1iwrg@mail.gmail.com>
Content-Language: en-US
In-Reply-To: <CAB-Bujb7MJ_+t7F1=EF5gKTgKsm44JnAUinN4nnwBf52q1iwrg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 5/29/24 21:53, Andreas Hennings wrote:
> Is there a reason why we cannot just make it "public private string
> $x" instead of "public private(set) string $x"?
> We would define that the second visibility specifier is for write.
> 
> The current proposal with "public private(set)" is less ambiguous, and
> it is immediately obvious that this is something new, and not just
> somebody accidentally added two modifiers.
> At the same time, it feels a bit alien and cluttered.
> 
> Other options could be something like "public:private" or "public-private".

The variant with the parentheses is the most future-proof one, should 
additional operations be added. It would allow for:

     public private(set,unset,frobnicate) string $foo;

Even if tools would not yet understand whatever 'frobnicate' does, they 
would know that this is an operation that may be performed on $foo and 
would be able to syntax highlight the visibility definition properly and 
they would also know how to autoformat it, without needing to add 
support for the new keyword.

Best regards
Tim Düsterhus