Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127185
Message-ID: <c70b3646-72ac-45bf-82bc-54c35c69b7b7@bastelstu.be>
Date: Thu, 24 Apr 2025 17:20:56 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] Re: RFC: Nested Classes
To: Rob Landers <rob@bottled.codes>, internals@lists.php.net
References: <aae32397-0567-417f-adbe-6b663d5c49ae@app.fastmail.com>
 <48dce917-d147-456b-9f03-c7e23411adff@app.fastmail.com>
 <AM8P250MB0170601416CA1D75F128D80FE2D92@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <8a16b81c-7dab-4523-a352-76ba0cb4e771@app.fastmail.com>
 <AM8P250MB0170CA8F8094797B55ADE424E2D82@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <9c4ac301-dfb2-49da-90e5-37a2824fc4e3@app.fastmail.com>
 <AM8P250MB0170330066F90E056EBA76F8E2D82@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <5b1e6d70-a1c9-455c-93d3-6b22cf1fef11@app.fastmail.com>
 <CAF-mU4zuja0XfemEyC8sJs=+in6Q6F3An7fzWB9+1o31o=Y-8w@mail.gmail.com>
 <efcac45a-60ac-4145-b012-72d5fef0090c@app.fastmail.com>
 <52d84a5b-09d3-4e42-9620-a62fb239c21e@app.fastmail.com>
 <09a82882-f1ee-4bdb-8a27-e46144a711f1@app.fastmail.com>
 <706e22d7-94eb-44bd-a280-f629ba93b630@app.fastmail.com>
 <03a5b9a8-9fe1-4656-ab04-dd58669488b3@app.fastmail.com>
 <158a5d7c-8ef6-4b5f-b8ef-593879a7a896@bastelstu.be>
 <a2f7ddb0-868e-49d6-b9fe-58d67ec15b08@app.fastmail.com>
Content-Language: en-US
In-Reply-To: <a2f7ddb0-868e-49d6-b9fe-58d67ec15b08@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 4/24/25 17:09, Rob Landers wrote:
> Thank you for your feedback! I think you would then have the problem that was pointed out by Levi the other day; where you would then have ambiguity. If you could have both private and public names in the same namespace, then you would end up not knowing which one was being referred to.

That is a design error in the RFC then.

> Also, it is worth pointing out that private symbols are *not* "invisible" or "non-existent" from outside classes. They emit their own errors: https://3v4l.org/PEGeA that indicate you tried to access something you shouldn't be able to. This is different than when you try to access something that actually doesn't exist: https://3v4l.org/nWVPV

Fair enough about the error message. You can also access them with 
Reflection or the Closure hack. They are nevertheless ”non-existent” 
from the public API PoV: https://3v4l.org/Us6VV

     <?php

     class Foo {
	private string $bar = "foo";
	private function foo(): array {}
     }

     class Bar extends Foo {
         private array $bar = [];

         private function foo($foo): int {}
     }

     class Baz extends Bar {
         public self $bar;
     }

     $baz = new Baz();
     $baz->bar = $baz;

     var_dump($baz);

In subclasses I can “redefine” private properties or methods and they do 
not interact at all. Properties have separate storage locations and can 
have differing types. Methods do not need to have compatible signatures 
either.

Best regards
Tim Düsterhus