Re: RFC Proposal - static modifier for classes
| From: | Rowan Tommins | Date: | Thu, 23 Nov 2023 10:21:49 +0000 |
| Subject: | Re: RFC Proposal - static modifier for classes | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-121776@lists.php.net to get a copy of this message | ||
On Thu, 23 Nov 2023 at 06:00, Stephen Reay <php-lists@koalephant.com> wrote:
> I'm disappointed to see yet again that there's this implied notion that
> working with PHP in 2023 means "well surely you must be using composer",
> which leads to "but composer..." somehow being an accepted argument when
> it comes to missing/incomplete builtin functionality.
>
While I appreciate your point in the general case, in this particular
thread, the mentions of Composer are really just examples, or can be
reworded that way:
Functions lack autoloading, but in practice this isn't a big problem
because you can just require_once a file defining them, and as long as
OpCache is running there's very little performance penalty. If you're using
a package manager or module loading system to integrate multiple
autoloaders, it's generally easy to add one or more required files as part
of the package / module config - *for example* Composer has a "files" array
in each package's "autoload" config.
So the actual assumption is "surely you must be using OpCache", which
unlike Composer is bundled with PHP.
Regards,
--
Rowan Tommins
[IMSoP]