Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123633
Feedback-ID: ifab94697:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-515-g87b2bad5a-fm-20240604.001-g87b2bad5
Precedence: bulk
MIME-Version: 1.0
Message-ID: <adb0e17c-c5b8-4e82-9d78-b09355f8a5fa@app.fastmail.com>
In-Reply-To: <D53A9527-EE4B-4DC2-9CA4-A982EF236917@rwec.co.uk>
References: <0cf69a14-f1b5-4077-9d91-d7b579485eec@scriptfusion.com>
 <936e1aa3-48cc-4552-9f68-676ebcdeb596@rwec.co.uk>
 <1fc2f2d0-718f-45ec-8968-b66a1bde686e@scriptfusion.com>
 <c2472dca-a297-4f14-bf53-b0ab9a67d3c7@rwec.co.uk>
 <b6d67db7-6689-4a1c-ad62-32cc96a01392@scriptfusion.com>
 <CAPyeZ4NW3eoaaXonM8bTHmji0a=CpWx7m8B5h_X44-eFDfOQbw@mail.gmail.com>
 <D53A9527-EE4B-4DC2-9CA4-A982EF236917@rwec.co.uk>
Date: Sun, 16 Jun 2024 14:28:19 +0200
To: internals@lists.php.net
Subject: Re: [PHP-DEV] Static class
Content-Type: multipart/alternative;
 boundary=368238be1c72421cb62feecdc094fb35
From: rob@bottled.codes ("Rob Landers")

--368238be1c72421cb62feecdc094fb35
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Sun, Jun 16, 2024, at 14:13, Rowan Tommins [IMSoP] wrote:
>=20
>=20
> On 15 June 2024 18:39:20 BST, Valentin Udaltsov <udaltsov.valentin@gma=
il.com> wrote:
>=20
> >PHP does not have internal/private functions.
> >Very often I use functions for really simple things like `array_flatt=
en`
> >(and register them via composer.json.autoload.files). But when the fu=
nction
> >requires decomposition to smaller ones, I switch to a static class wi=
th one
> >public and some private static methods.
>=20
> Namespace visibility or a native "internal" attribute is something tha=
t would be really useful, I think, because it would be able to apply to =
whole classes as well as functions and constants. It would also allow yo=
u to make the refactoring you mention without having to switch all calls=
 from Foo\bar() to Foo::bar()
>=20
> In general, I think PHP should embrace the concept of "packages" much =
more - for larger apps, there's a much greater scope for performance if =
OpCache could analyse multiple files at once, and make assumptions about=
 them. (A consideration which didn't apply when autoloading was first in=
troduced.)
>=20
> With that in mind, instead of function autoloading, maybe we should th=
ink about an "include_all" function, which accepted a wildcard/glob patt=
ern. That would make it much easier to use preloading, and move away fro=
m the "one class per file" layout, without blessing an official tool lik=
e Composer, or a particular file layout.
>=20
> Put together, those features would provide a powerful alternative to a=
 lot of static classes - i.e. those where no state or inheritance is req=
uired, just a grouping of code.
>=20
> Regards,
> Rowan Tommins
> [IMSoP]
>=20

Considering that I brought up an internal attribute not too long ago and=
 it seems like =E2=80=9Cpackaging=E2=80=9D is a giant can of worms, I=E2=
=80=99d like to suggest we don=E2=80=99t even approach the topic. People=
 on this list have very specific ideas of what that means and unless som=
eone is going to finally try championing an rfc after 30 years, it shoul=
dn=E2=80=99t even be a factor.=20

=E2=80=94 Rob
--368238be1c72421cb62feecdc094fb35
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}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div><br></div>=
<div><br></div><div>On Sun, Jun 16, 2024, at 14:13, Rowan Tommins [IMSoP=
] wrote:<br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><div><b=
r></div><div><br></div><div>On 15 June 2024 18:39:20 BST, Valentin Udalt=
sov &lt;<a href=3D"mailto:udaltsov.valentin@gmail.com">udaltsov.valentin=
@gmail.com</a>&gt; wrote:<br></div><div><br></div><div>&gt;PHP does not =
have internal/private functions.<br></div><div>&gt;Very often I use func=
tions for really simple things like `array_flatten`<br></div><div>&gt;(a=
nd register them via composer.json.autoload.files). But when the functio=
n<br></div><div>&gt;requires decomposition to smaller ones, I switch to =
a static class with one<br></div><div>&gt;public and some private static=
 methods.<br></div><div><br></div><div>Namespace visibility or a native =
"internal" attribute is something that would be really useful, I think, =
because it would be able to apply to whole classes as well as functions =
and constants. It would also allow you to make the refactoring you menti=
on without having to switch all calls from Foo\bar() to Foo::bar()<br></=
div><div><br></div><div>In general, I think PHP should embrace the conce=
pt of "packages" much more - for larger apps, there's a much greater sco=
pe for performance if OpCache could analyse multiple files at once, and =
make assumptions about them. (A consideration which didn't apply when au=
toloading was first introduced.)<br></div><div><br></div><div>With that =
in mind, instead of function autoloading, maybe we should think about an=
 "include_all" function, which accepted a wildcard/glob pattern. That wo=
uld make it much easier to use preloading, and move away from the "one c=
lass per file" layout, without blessing an official tool like Composer, =
or a particular file layout.<br></div><div><br></div><div>Put together, =
those features would provide a powerful alternative to a lot of static c=
lasses - i.e. those where no state or inheritance is required, just a gr=
ouping of code.<br></div><div><br></div><div>Regards,<br></div><div>Rowa=
n Tommins<br></div><div>[IMSoP]<br></div><div><br></div></blockquote><di=
v><br></div><div>Considering that I brought up an internal attribute not=
 too long ago and it seems like =E2=80=9Cpackaging=E2=80=9D is a giant c=
an of worms, I=E2=80=99d like to suggest we don=E2=80=99t even approach =
the topic. People on this list have very specific ideas of what that mea=
ns and unless someone is going to finally try championing an rfc after 3=
0 years, it shouldn=E2=80=99t even be a factor.&nbsp;<br></div><div><br>=
</div><div id=3D"sig121229152">=E2=80=94 Rob<br></div></body></html>
--368238be1c72421cb62feecdc094fb35--