Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124201
Feedback-ID: ifab94697:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-566-g3812ddbbc-fm-20240627.001-g3812ddbb
Precedence: bulk
MIME-Version: 1.0
Message-ID: <78465ebc-0e87-4033-babd-656e46fe8341@app.fastmail.com>
In-Reply-To: <1AFD7AAE-8BEA-460D-88A8-15BB3D30A775@koalephant.com>
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>
Date: Wed, 03 Jul 2024 17:04:51 +0200
To: "Stephen Reay" <php-lists@koalephant.com>,
 "Vincent de Lau" <vincent@delau.nl>
Cc: "PHP internals" <internals@lists.php.net>
Subject: Re: [PHP-DEV] Iteration III: Packages (was Re: [PHP-DEV] [Initial Feedback]
 PHP User Modules - An Adaptation of ES6 from JavaScript)
Content-Type: multipart/alternative;
 boundary=d7e87f40edb8494792427bc4f9c0b357
From: rob@bottled.codes ("Rob Landers")

--d7e87f40edb8494792427bc4f9c0b357
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable


>> To come back to spl_autoload: That function pre-dates namespaces and =
is highly opinionated on how to organise code. All lower-case filenames,=
 class per-file, files in include_path, full namespace in path, you name=
 it. If that is what projects wanted at the time, or even now, PSR-0 and=
 the PHP-FIG would possibly not even exist.
>>=20
>=20
> It's less highly opinionated than either PSR, but that's my whole poin=
t: it's *someone else's opinion*, hence it's opposed by FIG.
>=20
>=20
>=20
> Neither of which is the point I was making - someone claimed that auto=
loaders are implicitly userland code. The point is they don't *have* to =
be, and there is a perfectly useable one built in to the SPL extension; =
if it's "too opinionated" (or the opinions are ones you don't like), it'=
s hardly the most in-depth of functions, and it already *has* configurab=
le parts, so adding in more control shouldn't exactly require a rocket s=
cientist to add, for example, the ability to use the original case of th=
e class name.

To be fair, I didn't know this was a thing (you learn something new ever=
y day) and I'd rather have all-lower-case filenames, so I may actually l=
ook into this. I wonder if composer exposes this as an option?

=E2=80=94 Rob
--d7e87f40edb8494792427bc4f9c0b357
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div><span style=3D"=
color:#000000;"></span><br></div><blockquote type=3D"cite" id=3D"qt" sty=
le=3D"overflow-wrap:break-word;"><div><div><blockquote type=3D"cite">To =
come back to spl_autoload: That function pre-dates namespaces and is hig=
hly opinionated on how to organise code. All lower-case filenames, class=
 per-file, files in include_path, full namespace in path, you name it. I=
f that is what projects wanted at the time, or even now, PSR-0 and the P=
HP-FIG would possibly not even exist.<br></blockquote></div><blockquote =
type=3D"cite"><div><div><br></div></div></blockquote><div><br></div><div=
>It's less highly opinionated than either PSR, but that's my whole point=
: it's *someone else's opinion*, hence it's opposed by FIG.<br></div><di=
v><br></div><div><br></div><div><br></div><div>Neither of which is the p=
oint I was making - someone claimed that autoloaders are implicitly user=
land code. The point is they don't *have* to be, and there is a perfectl=
y useable one built in to the SPL extension; if it's "too opinionated" (=
or the opinions are ones you don't like), it's hardly the most in-depth =
of functions, and it already *has* configurable parts, so adding in more=
 control shouldn't exactly require a rocket scientist to add, for exampl=
e, the ability to use the original case of the class name.<br></div></di=
v></blockquote><div><br></div><div>To be fair, I didn't know this was a =
thing (you learn something new every day) and I'd rather have all-lower-=
case filenames, so I may actually look into this. I wonder if composer e=
xposes this as an option?</div><div><br></div><div id=3D"sig121229152">=E2=
=80=94 Rob<br></div></body></html>
--d7e87f40edb8494792427bc4f9c0b357--