Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123632
Feedback-ID: id5114917:Fastmail
Date: Sun, 16 Jun 2024 13:13:52 +0100
To: internals@lists.php.net
Subject: Re: [PHP-DEV] Static class
User-Agent: K-9 Mail for Android
In-Reply-To: <CAPyeZ4NW3eoaaXonM8bTHmji0a=CpWx7m8B5h_X44-eFDfOQbw@mail.gmail.com>
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>
Message-ID: <D53A9527-EE4B-4DC2-9CA4-A982EF236917@rwec.co.uk>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")



On 15 June 2024 18:39:20 BST, Valentin Udaltsov <udaltsov=2Evalentin@gmail=
=2Ecom> wrote:

>PHP does not have internal/private functions=2E
>Very often I use functions for really simple things like `array_flatten`
>(and register them via composer=2Ejson=2Eautoload=2Efiles)=2E But when th=
e function
>requires decomposition to smaller ones, I switch to a static class with o=
ne
>public and some private static methods=2E

Namespace visibility or a native "internal" attribute is something that wo=
uld be really useful, I think, because it would be able to apply to whole c=
lasses as well as functions and constants=2E It would also allow you to mak=
e the refactoring you mention without having to switch all calls from Foo\b=
ar() to Foo::bar()

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=2E (=
A consideration which didn't apply when autoloading was first introduced=2E=
)

With that in mind, instead of function autoloading, maybe we should think =
about an "include_all" function, which accepted a wildcard/glob pattern=2E =
That would make it much easier to use preloading, and move away from the "o=
ne class per file" layout, without blessing an official tool like Composer,=
 or a particular file layout=2E

Put together, those features would provide a powerful alternative to a lot=
 of static classes - i=2Ee=2E those where no state or inheritance is requir=
ed, just a grouping of code=2E

Regards,
Rowan Tommins
[IMSoP]