Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124363
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>
 <CAMrTa2EvD3qcTL5SoXwAJ6kT5NTu0QLSQjjJRa0z-esUMVxj6w@mail.gmail.com>
 <1BE6A849-A2A9-4E17-9C11-5099EF74F5C0@rwec.co.uk> <B814CAB0-50DA-4EB3-97EE-72542EFCD184@newclarity.net>
 <1d0df8f2-541a-4302-a658-4d7d30003342@seld.be>
In-Reply-To: <1d0df8f2-541a-4302-a658-4d7d30003342@seld.be>
Date: Wed, 10 Jul 2024 14:08:39 -0400
Message-ID: <CAEUnE0dryTVVkBU0stYMrJbbBqRTK332PXgiYm-7ddDB5c1dhA@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="000000000000e442d8061ce889c3"
From: tendoaki@gmail.com (Michael Morris)

--000000000000e442d8061ce889c3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 10, 2024 at 5:51=E2=80=AFAM Jordi Boggiano <j.boggiano@seld.be>=
 wrote:

>
> As for the rest of the thread, I feel like everyone needs to take a few
> days to chill because it's getting a bit heated around here.
>
People are passionate about the things they love.  I've been busy with work
and on Iteration V.  Details later this week, likely in the form of a
github repo hosted markdown file that will be easier to follow, as the
number of points to address is getting too lengthy to deal with in a list
conversation and, more worryingly, people are glomming onto and criticizing
the proposal for things already dropped.

In particular - I'm not talking about ditching composer.  I don't want to
get in the business of building a package manager, especially when there's
an existing one.

Some highlights of what I am working on

1. Import Maps - These would be prepared by hand or by a package manager
like composer. An internal autoloader will work with them. Unlike autoload
functions, import maps get merged together so the actual seek operation can
remain optimized.  Given Composer already can build an optimized class map
file it is already well positioned to feed information into this code. The
reason to use it is that it will be able to detect symbols the autoload
system cannot: functions and constants. It will also be able to load
packages and modules.
2. Packages - Packages load differently and can effectively monkey-type the
code of an existing package on the fly in much the same way that namespaces
themselves work with symbol names as a flat string replace. Existing code
can be loaded into packages, but also an outline for writing packages that
have privacy modifiers to their members - i.e. protected class SomeClass {}
3. Modules - Files which are code first instead of template first.

These are being prepped as at least 3 interrelated RFC drafts which can be
dealt with piecemeal, and any of the three not receiving enough support for
inclusion doesn't preclude the others from going forward.

--000000000000e442d8061ce889c3
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 10, 2024 at 5:51=E2=80=AF=
AM Jordi Boggiano &lt;<a href=3D"mailto:j.boggiano@seld.be">j.boggiano@seld=
.be</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><u></u>

 =20
   =20
 =20
  <div>
    <div><br></div>
    <p>As for the rest of the thread, I feel like everyone needs to take
      a few days to chill because it&#39;s getting a bit heated around here=
.</p></div></blockquote><div>People are passionate=C2=A0about the things th=
ey love.=C2=A0 I&#39;ve been busy with work and on Iteration V.=C2=A0 Detai=
ls later this week, likely in the form of a github repo hosted markdown fil=
e that will be easier to follow, as the number of points to address is gett=
ing too lengthy=C2=A0to deal with in a list conversation and, more worrying=
ly, people are glomming onto and criticizing the proposal for things alread=
y dropped.</div><div><br></div><div>In particular - I&#39;m not talking abo=
ut ditching composer.=C2=A0 I don&#39;t want to get in the business of buil=
ding a package manager, especially when there&#39;s an existing one.</div><=
div><br></div><div>Some highlights of what I am working on</div><div><br></=
div><div>1. Import Maps - These would be prepared by hand or by a package m=
anager like composer. An internal autoloader will work with them. Unlike au=
toload functions, import maps get merged together so the actual seek operat=
ion can remain optimized.=C2=A0 Given Composer already can build an optimiz=
ed class map file it is already well positioned to feed information into th=
is code. The reason to use it is that it will be able to detect symbols the=
 autoload system cannot: functions and constants. It will also be able to l=
oad packages and modules.</div><div>2. Packages - Packages load differently=
 and can effectively monkey-type the code of an existing package on the fly=
 in much the same way that namespaces themselves work with symbol names as =
a flat string replace. Existing code can be loaded into packages, but also =
an outline for writing packages that have privacy modifiers to their member=
s - i.e. protected class SomeClass {}</div><div>3. Modules - Files which ar=
e code first instead of template first.</div><div><br></div><div>These are =
being prepped as at least 3 interrelated RFC drafts which can be dealt with=
 piecemeal, and any of the three not receiving enough support for inclusion=
 doesn&#39;t preclude the others from going forward.</div><div><br></div><d=
iv><br></div><div>=C2=A0</div></div></div>

--000000000000e442d8061ce889c3--