Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127458
Feedback-ID: id5114917:Fastmail
Message-ID: <1c6dcd84-9016-48e1-971f-de7749cbdce8@rwec.co.uk>
Date: Sun, 25 May 2025 23:17:56 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Module or Class Visibility, Season 2
Content-Language: en-GB
To: internals@lists.php.net
References: <CADK1yXKg1xpneLs3vJ=nUAAGaVuBhqkEMgbBVaYfcBfQL2vkDg@mail.gmail.com>
 <9A26F72B-D0EF-414F-B193-BED3CAB26A0B@rwec.co.uk>
 <9f6a0d6e-27c3-4f77-aed6-e55147442b6f@app.fastmail.com>
 <B46C391D-2248-4E54-BFBE-2195FFB6A2A5@rwec.co.uk>
 <ca5c49c9-948a-48f0-8b94-86fea583fbc4@app.fastmail.com>
 <673fd2db-b07f-439b-a4f2-e9519108d159@app.fastmail.com>
 <CAEUnE0dxRwjhKC64XHWkF3bNRLgjkgSJ9oMajRPfwLoDWy3x-g@mail.gmail.com>
 <78641D8B-AF1D-4912-920A-D75A37C32F05@rwec.co.uk>
 <CAEUnE0dVyQ9NQonEBU6wkKM+WsyLXt68jAGYjsz270w_Fa8=Fw@mail.gmail.com>
 <CF275E74-F6AE-4357-8586-2FF17DC84FB5@rwec.co.uk>
 <CAEUnE0eR-0c=pDxgFrB4n60rGescZDVzOgb4uJbYK1aLvQE8=A@mail.gmail.com>
 <354cb888-97c4-4f8c-a0da-359d1e63c0f9@rwec.co.uk>
 <CAEUnE0dffEmFHV872btX5x_mbwmRmY1GCw+OPPrtr6sLD+u_zg@mail.gmail.com>
 <10D95B6E-094B-4EAE-A18A-AF6B795CB352@rwec.co.uk>
 <2adbff61-5e11-4d39-ab5c-d7950a4550a6@app.fastmail.com>
 <79E7FA26-2F5A-470C-B1DF-12CC46A08FE5@rwec.co.uk>
 <cda01760-9f0e-48e4-801d-f436243e088c@app.fastmail.com>
In-Reply-To: <cda01760-9f0e-48e4-801d-f436243e088c@app.fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

On 25/05/2025 21:28, Larry Garfield wrote:
> Even if we develop some way such that in Foo.php, loading the class \Beep\Boop\Narf pulls from /beep/boop/v1/Narf.php and loading it from Bar.php pulls the same class from /beep/boop/v2/Narf.php, and does something or other to keep the symbols separate... Narf itself is going to load \Beep\Boop\Poink at some point.  So which one does it get?  Or rather, there's now two Narfs.  How do they know that the v1 version of Narf should get the v1 version of Poink and the v2 version should get the v2 version.


The prefixing, in my mind, has nothing to do with versions. There is no 
"v1" and "v2" directory, there are just two completely separate "vendor" 
directories, with the same layout we have right now.

So it goes like this:

1. Some code in wp-plugins/AlicesCalendar/vendor/Beep/Boop/Narf.php 
mentions a class called \Beep\Boop\Poink
2. The Container mechanism has rewritten this to 
\__Container\AlicesCalendar\Beep\Boop\Poink, but that isn't defined yet
3. The isolated autoloader stack (loaded from 
wp-plugins/AlicesCalendar/vendor/autoload.php) is asked for the original 
name, \Beep\Boop\Poink
4. It includes the file 
wp-plugins/AlicesCalendar/vendor/Beep/Boop/Poink.php which contains the 
defintion of \Beep\Boop\Poink
5. The Container mechanism rewrites the class to 
\__Container\AlicesCalendar\Beep\Boop\Poink and carries on

When code in wp-plugins/BobsDocs/vendor/Beep/Boop/Narf.php mentions 
\Beep\Boop\Poink, the same thing happens, but with a completely separate 
sandbox: the rewritten class name is 
\__Container\BobsDocs\Beep\Boop\Poink, and the autoloader was loaded 
from wp-plugins/BobsDocs/vendor/autoload.php

Unless explciitly specified as an "import" or "export", any reference to 
any class name is prefixed in the same way, and loaded with the isolated 
autoloader stack. To the host application, and any other plugins, the 
code inside the "wp-plugins/AlicesCalendar/vendor" and 
"wp-plugins/BobsDocs/vendor" directories is entirely hidden.

-- 
Rowan Tommins
[IMSoP]