Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129174
Message-ID: <dd203c8e-7b88-4558-b6d5-77c8dc873780@bastelstu.be>
Date: Sun, 9 Nov 2025 19:01:50 +0100
Precedence: list
MIME-Version: 1.0
Subject: Re: [PHP-DEV] RFC: Namespace-Scoped Visibility for Methods and
 Properties
To: Rob Landers <rob@bottled.codes>, =?UTF-8?B?QWxleGFuZHJ1IFDEg3RyxINuZXNj?=
 =?UTF-8?Q?u?= <drealecs@gmail.com>
Cc: PHP internals <internals@lists.php.net>
References: <e21b1992-d426-46cd-b86a-6d6a5844c934@app.fastmail.com>
 <CAAwdEzAOX4rang8Je-1gaA=SxA67xb-EnFBh4648=2SKABoBxA@mail.gmail.com>
 <a2403c73-26af-410b-baf9-381b15e7c255@app.fastmail.com>
 <d2e6cadb-9778-4e0d-8fda-efb430b477c6@app.fastmail.com>
Content-Language: en-US
In-Reply-To: <d2e6cadb-9778-4e0d-8fda-efb430b477c6@app.fastmail.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 11/9/25 16:07, Rob Landers wrote:
> I’ve updated the RFC and implementation accordingly along with some editorial changes.

The RFC now mentions:

> Combinations that mix protected and private with private(namespace)(set) are a compile-time error because their allowed caller sets aren’t subsets of each other.

Which is not particularly explicit in what “mix” means. I initially 
missed the `(set)` in the `private(namespace)(set)` until I read the ML 
discussion.

 From what I see the RFC does not discuss the following at all:

     class P {
         protected function x() { }
     }
     class C extends P {
         private(namespace) function x() { }
     }

and vice versa:

     class P {
         private(namespace) function x() { }
     }
     class C extends P {
         protected function x() { }
     }

Best regards
Tim Düsterhus