Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127450
Feedback-ID: id5114917:Fastmail
Date: Sat, 24 May 2025 22:18:41 +0100
To: internals@lists.php.net
Subject: Re: [PHP-DEV] Module or Class Visibility, Season 2
User-Agent: K-9 Mail for Android
In-Reply-To: <2adbff61-5e11-4d39-ab5c-d7950a4550a6@app.fastmail.com>
References: <CADK1yXKg1xpneLs3vJ=nUAAGaVuBhqkEMgbBVaYfcBfQL2vkDg@mail.gmail.com> <CAEUnE0d8QADSYv+OJMEceN4hdJNcNy=-GLvW-ZoNqoi6_2Lhxw@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>
Message-ID: <79E7FA26-2F5A-470C-B1DF-12CC46A08FE5@rwec.co.uk>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

On 24 May 2025 14:11:57 BST, Rob Landers <rob@bottled=2Ecodes> wrote:
>My only concern is how this would be handled in the class tables=2E Right=
 now, \AlicesCalendar\Monolog\Logger and \BobsDocs\Monolog\Logger would be =
considered entirely different types -- as in, not compatible=2E So if Alice=
sCalendar returns a type that BobsDocs expects, they won't be able to talk =
to each other=2E

Once again, I'd like to use the Linux Container analogy: a process in one =
container never communicates directly with a process in another container=
=2E The process "thinks" it's running as normal, but is actually isolated i=
nside a sandbox=2E The container then defines the inputs and outputs it wan=
ts to open between that sandbox and the host, and something running on the =
host can wire those up as necessary=2E



>I assume that it will be up to a dependency resolver (either composer or =
something else) will need to figure out which direct dependencies to "hoist=
" up and provide a compatible version between the two packages=2E

I see this as the responsibility of each "container": if AlicesCalendar wa=
nts to use an un-sandboxed version of a PSR interface or a framework compon=
ent, it declares that to the "host" (e=2Eg=2E WordPress core)=2E The PHP en=
gine then knows to leave that interface name without a prefix=2E Any other =
class - whether it's written by Alice or installed by Composer - exists ins=
ide the sandbox, and gets a prefix=2E

Importantly, all of this should happen on the *PHP symbol* level (classes,=
 interfaces, functions); the sandboxing mechanism doesn't need to know abou=
t package managers - just as Docker, Kunernetes, etc, don't know about APT =
/ Yum / whatever Apine calls it=2E

Rowan Tommins
[IMSoP]