> On May 7, 2020, at 21:02, Mike Schinkel <m...@newclarity.net> wrote: > > One potential option that comes to mind is a standard library of PHP-written > functionality bundled in a PHAR file that would be included with future > implementations of PHP and automatically included by PHP.
This was the gist of Larry’s comments on the other thread[1]. Pasted here, for reference: > Between preloading, PHP 7's improvements, FFI funkiness, > and the upcoming JIT, there's been on and off discussion > about moving much of the standard library from C to "PHP > code that is bundled and preloaded automatically." A real > "standard library" in PHP, rather than a bunch of bridged > C functions that exist for the legacy reasons Dan notes > above. > > Making that actually a thing would help obviate a lot of > these issues, I think. It becomes no longer an > implementation question but "just" a packaging question. It wouldn’t need to be a PHAR file, but the general idea is the same: move a lot of the stuff that can be implemented (without losing performance) into pure PHP code, while keeping it part of php-src, and somehow package and bundle it with the `php` binary (or otherwise include it so that those symbols are loaded when PHP “starts up”). IIRC, HHVM also does something like this (or did), and I would be in favor of this in PHP. Cheers, Ben [1]: https://externals.io/message/109972#110071
signature.asc
Description: Message signed with OpenPGP
