[PHP-DEV] No longer allow block mode for declare(encoding)

2022-08-31 Thread Christoph M. Becker
Hi all, recently, there was a bug report regarding declare(encoding)[1]. I've checked that, and found that the current implementation of declare(encoding) doesn't make sense regarding "block mode", since this is completely ignored; instead, each (allowed) declare(encoding) works from where it is

Re: [PHP-DEV] No longer allow block mode for declare(encoding)

2022-08-31 Thread Sara Golemon
On Wed, Aug 31, 2022 at 10:43 AM Christoph M. Becker wrote: > recently, there was a bug report regarding declare(encoding)[1]. I've > checked that, and found that the current implementation of > declare(encoding) doesn't make sense regarding "block mode", since this > is completely ignored; inst

Re: [PHP-DEV] [RFC] Asymmetric visibility

2022-08-31 Thread Larry Garfield
On Fri, Aug 5, 2022, at 12:08 PM, Larry Garfield wrote: > Ilija Tovilo and I are happy to present the first new RFC for PHP 8.3: > Asymmetric Visibility. > > https://wiki.php.net/rfc/asymmetric-visibility > > Details are in the RFC, but it's largely a copy of Swift's support for the > same. Hi f

Re: [PHP-DEV] No longer allow block mode for declare(encoding)

2022-08-31 Thread Hans Henrik Bergan
>it might be hard to properly implement support No effort should be wasted supporting this. +1 On Wed, Aug 31, 2022, 21:21 Sara Golemon wrote: > On Wed, Aug 31, 2022 at 10:43 AM Christoph M. Becker > wrote: > > > recently, there was a bug report regarding declare(encoding)[1]. I've > > checke

Re: [PHP-DEV] [RFC] Asymmetric visibility

2022-08-31 Thread Tim Düsterhus
Hi On 8/31/22 22:43, Larry Garfield wrote: ## References make everything worse […] That problem wouldn't happen if all we're changing is visibility, however. That means in the C# style, we would need to differentiate whether the block on the right is intended to disable references or not.

Re: [PHP-DEV] [RFC] Asymmetric visibility

2022-08-31 Thread Claude Pache
> Le 31 août 2022 à 23:27, Tim Düsterhus a écrit : > I've read through that explanation three times, but don't understand why the > C#-style syntax would require to differentiate between `set` and `raw`. Isn't > the difference between "visibility only" and "accessor" not clear [1] by > havin

Re: [PHP-DEV] [RFC] Asymmetric visibility

2022-08-31 Thread Larry Garfield
On Wed, Aug 31, 2022, at 4:26 PM, Tim Düsterhus wrote: > Hi > > On 8/31/22 22:43, Larry Garfield wrote: >> ## References make everything worse >> >> […] >> >> That problem wouldn't happen if all we're changing is visibility, however. >> That means in the C# style, we would need to differentiate