Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124225
Precedence: bulk
MIME-Version: 1.0
References: <09559430-4477-4516-8D78-6F4071E1AA6C@newclarity.net>
 <0182F3D6-F464-477F-9029-A2D0A8B50C71@koalephant.com> <GV1PR01MB10526D0B220ED0AC9D1C17473C2DD2@GV1PR01MB10526.eurprd01.prod.exchangelabs.com>
 <1AFD7AAE-8BEA-460D-88A8-15BB3D30A775@koalephant.com> <CAJp_myXHSHD6+76gyOs=d+cfVgwCmpuhKMtYcVBM6b-i3Bf0WQ@mail.gmail.com>
 <CAEUnE0dObGkb+jUZrVhNRg0JHaM5Kt9d93k3p_0D=jX7kxmYAg@mail.gmail.com>
 <e42cd46b-d98b-4567-a854-03ca54d4dbcf@app.fastmail.com> <CAEUnE0cQA-QrmDmAjpBm=sXkE58Y4ODbNwPYY=QBJV46Q8nR9g@mail.gmail.com>
 <CAEUnE0eEjsBXmz8AEVG1SKE=i08-9dit1ze1K0mWrdyQt4okqQ@mail.gmail.com>
 <7B633CC7-C768-4852-A4D0-B252A04F7DE1@newclarity.net> <CAEUnE0fFfggyvtNGMytWATG7xUrwfjtXp5F0Sk9PvXo-1Rf+_g@mail.gmail.com>
 <0E11F373-99DC-496E-9BBC-2F8688B9F66A@newclarity.net>
In-Reply-To: <0E11F373-99DC-496E-9BBC-2F8688B9F66A@newclarity.net>
Date: Thu, 4 Jul 2024 21:16:11 -0400
Message-ID: <CAEUnE0fMGzYimJr71VSFr44FQPBzszfd7FbScfwYx794GZMsrQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [PHP-Dev] Versioned Packagers (Iteration IV)
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b687b4061c75cf76"
From: tendoaki@gmail.com (Michael Morris)

--000000000000b687b4061c75cf76
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 3, 2024 at 11:11=E2=80=AFPM Mike Schinkel <mike@newclarity.net>=
 wrote:

> >>   import 'file.php v1.0.0';
> >
> > Where will PHP be able to get the version number in a performant manner=
?
> >
> > A question for another day.
>
> Frankly if your proposal hinges on using version numbers to differentiate
> then I think it is not something you can postpone answering.
>
> If there is not a good answer then the approach you are exploring is moot=
,
> at least as far as I can see.
>
>
So I've had more time to mull this over, and some research, and I think I
have an approach.

First, instead of 'import', use 'require_module'.  The parsing rules for
require_module differ from require how the file is parsed, a subject for
another time.  Also, it's parallel to what is to follow.

Speaking of new functions, let's start with these

  spl_set_include_ini_map('importmap.ini');
  spl_set_include_json_map('importmap.json")

The json file is pretty much identical to the JavaScript importmaps. The
ini file looks like this

  root =3D "/absolute/path/to/application/root"

  [imports]
  square =3D "./path/to/square.js"
  circle =3D "./path/to/circle.js"
  other/ =3D "./path/to/other/"

  [scopes]
  \A[square] =3D './path/to/square/in/namespace/A/a.js'

Whichever format is used is a matter of personal preference. The file can
be, and likely should be, written by composer or some future package
manager.

The root attribute in the map sets the root for all relative paths given in
the map.

Imports are the standard imports for the project.  The token on the left
maps to the target on the right.
Import maps affect all includes.  Import map tokens are considered before
anything use on the include resolution rules.  So `include 'square'` would
bring in '/absolute/path/to/application/root/path/to/square.js' given the
ini file above.

An import token ending in / is a prepend and the path it maps to must also
end in a slash.  So `require_module 'other/triangle.php' will map to
'/absolute/path/to/application/root/path/to/other/triangle.php' given the
ini file above.

Scopes have a namespace followed by the token in brackets.  Scopes only
affect require_module as the other include mechanisms do not pay attention
to namespaces.  When in that namespace the specified file will be loaded
instead of the default outlined in imports.

The import map system is inspired by but not exactly like JavaScript's
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/impor=
tmap

This approach gets whatever RFC that comes out of this proposal out of the
business of trying to design a package manager.

--000000000000b687b4061c75cf76
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 3, 2024 at 11:11=E2=80=AF=
PM Mike Schinkel &lt;<a href=3D"mailto:mike@newclarity.net">mike@newclarity=
.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">&gt;&gt;=C2=A0 =C2=A0import &#39;file.php v1.0.0&#39;;<br>
&gt; <br>
&gt; Where will PHP be able to get the version number in a performant manne=
r?<br>
&gt; <br>
&gt; A question for another day.<br>
<br>
Frankly if your proposal hinges on using version numbers to differentiate t=
hen I think it is not something you can postpone answering. <br>
<br>
If there is not a good answer then the approach you are exploring is moot, =
at least as far as I can see.<br><br></blockquote><div><br></div><div>So I&=
#39;ve had more time to mull this over, and some research, and I think I ha=
ve an approach.</div><div><br></div><div>First, instead of &#39;import&#39;=
, use &#39;require_module&#39;.=C2=A0 The parsing rules for require_module =
differ from require how the file is parsed, a subject for another time.=C2=
=A0 Also, it&#39;s parallel to what is to follow.</div><div><br></div><div>=
Speaking of new functions, let&#39;s start with these</div><div><br></div><=
div>=C2=A0 spl_set_include_ini_map(&#39;importmap.ini&#39;);<br>=C2=A0 spl_=
set_include_json_map(&#39;importmap.json&quot;)</div><div><br></div><div>Th=
e json file is pretty much identical to the JavaScript importmaps. The ini =
file looks like this</div><div><br></div><div><font face=3D"monospace">=C2=
=A0 root =3D &quot;/absolute/path/to/application/root&quot;</font></div><di=
v><font face=3D"monospace"><br></font></div><font face=3D"monospace">=C2=A0=
 [imports]<br>=C2=A0 square =3D &quot;./path/to/square.js&quot;<br>=C2=A0 c=
ircle =3D &quot;./path/to/circle.js&quot;<br>=C2=A0 other/ =3D &quot;./path=
/to/other/&quot;<br><br>=C2=A0 [scopes]<br>=C2=A0 \A[square] =3D &#39;./pat=
h/to/square/in/namespace/A/a.js&#39;</font><div>=C2=A0</div><div>Whichever =
format is used is a matter of personal preference. The file can be, and lik=
ely should be, written by composer or some future package manager.</div><di=
v><br></div><div>The root attribute in the map sets the root for all relati=
ve paths given in the map.</div><div><br></div><div>Imports are the standar=
d imports for the project.=C2=A0 The token on the left maps to the target o=
n the right.=C2=A0=C2=A0</div><div>Import maps affect all includes.=C2=A0 I=
mport map tokens are considered before anything use on the include resoluti=
on rules.=C2=A0 So `include &#39;square&#39;` would bring in &#39;/absolute=
/path/to/application/root/path/to/square.js&#39; given the ini file above.<=
/div><div><br></div><div>An import token ending in / is a prepend and the p=
ath it maps to must also end in a slash.=C2=A0 So `require_module &#39;othe=
r/triangle.php&#39; will map to &#39;/absolute/path/to/application/root/pat=
h/to/other/triangle.php&#39; given the ini file above.</div><div><br></div>=
<div>Scopes have a namespace followed by the token in brackets.=C2=A0 Scope=
s only affect require_module as the other include mechanisms do not pay att=
ention to namespaces.=C2=A0 When in that namespace the specified file will =
be loaded instead of the default outlined in imports.</div><div><br></div><=
div>The import map system is inspired by but not exactly like JavaScript=
9;s=C2=A0<a href=3D"https://developer.mozilla.org/en-US/docs/Web/HTML/Eleme=
nt/script/type/importmap">https://developer.mozilla.org/en-US/docs/Web/HTML=
/Element/script/type/importmap</a></div><div><br></div><div>This approach g=
ets whatever RFC that comes out of this proposal out of the business of try=
ing to design a package manager.</div><div><br></div><div><br></div></div><=
/div>

--000000000000b687b4061c75cf76--