Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124185
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: [PHP-DEV] Iteration III: Packages (was Re: [PHP-DEV] [Initial
 Feedback] PHP User Modules - An Adaptation of ES6 from JavaScript)
Date: Tue, 2 Jul 2024 23:32:08 -0600
References: <CAEUnE0fGZ3jFiBG=GyvnhBzH5a0iO4=n75PM=3+6zLAMrumEvA@mail.gmail.com>
 <CADK1yX+E9mvaM_CHJ8tmEx=O70hf8xasbvngh4wvNM8ce8KKGQ@mail.gmail.com>
 <B5DC69B8-E044-47FB-B81C-307E2C19CB66@newclarity.net>
 <1917CF7C-26D8-4DBE-B05C-5AA650AC6C9F@rwec.co.uk>
 <551cd5b0-1c00-4818-a9ca-97f6b7e8c3dc@app.fastmail.com>
 <CAEUnE0fNxSHN4QGfm6ETMVdE5Mcm1AEebmWs7i9xDNgcWnvQvw@mail.gmail.com>
 <39B496F8-062E-4848-9B3B-529BE8D3415A@newclarity.net>
 <CAEUnE0fOfU1tJNKXuBqbSm8jsp7gqe_JY-SiipdUKNztcx0Rog@mail.gmail.com>
 <856F4F70-DC81-4098-82DD-5F6D47CDF3F0@newclarity.net>
 <CAEUnE0c0fW9xnQOtLgj1zTpvdfixSHuLeLA7HOqDTkpr4hJ84g@mail.gmail.com>
 <CAEUnE0dSUY2VKji_o-AgQ-YZMf7viwCZh1sa8ScHdS7ihUgfUQ@mail.gmail.com>
 <CAL0xaBFWUkeMk=ofOF4q+keVN6X3nx67NjZ1-2zWfgGez1oy4Q@mail.gmail.com>
 <09559430-4477-4516-8D78-6F4071E1AA6C@newclarity.net>
 <4D45294E-78BA-466A-B2B4-F17BA4E1ED73@woofle.net>
To: php internals <internals@lists.php.net>
In-Reply-To: <4D45294E-78BA-466A-B2B4-F17BA4E1ED73@woofle.net>
Message-ID: <6C3C9DCE-0DC8-4470-AE2B-28E550E08774@miles.systems>
From: richard@miles.systems (Richard Miles)

Howdy people,

> On Jul 1, 2024, at 11:07=E2=80=AFAM, Dusk <dusk@woofle.net> wrote:
>=20
> On Jul 1, 2024, at 09:22, Mike Schinkel <mike@newclarity.net> wrote:
>> 2. Autoloading effectively necessitates that every symbol be in its =
own separate file.
>=20
> How so? While Composer "recommends" PSR4 autoloading with one class =
per file, other configurations are entirely possible, either with =
Composer's autoload.classmap (which uses a precomputed class -> filename =
table), or with a custom autoloader.


If I'm understanding the main issue, we need package-level scope.=20
Rather than build a whole new thing, what if we solve this problem?=20

Thought:
What if php implicitly prepended namespaces with the composer package =
version?
If two incompatible versions are required, the composer downloads both. =
Enabled/Disabled with flag?

Maybe: org/package/version/

This implicit version would show in debug backtraces. So importing =
Example\Example; might look like this in the trace:

1.0.8\Example\Example

Packages imports by namespace could automatically resolve to the version =
defined in that file's local package JSON.
Reflection to know where the code is running is easy enough, but this =
would require interpreter-level changes.
It=E2=80=99s a little late, but off the top of my head, it seems fairly =
backward-compatible.=20
However, if someone relies on parsing a stack trace=E2=80=A6 hmmm (trace =
flag too?)

Contextual sidenote:
Mac doesn=E2=80=99t ship with brew. Windows doesn=E2=80=99t ship with =
Chocloaty.
Python ships with pip, and Node ships with npm.=20
Python didn=E2=80=99t start shipping with pip until version >=3D 3.4.=20

I would be happy to see PHP shipping with the composer as a =
default-enabled flag.

Best,
Richard Miles=