Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110080
Message-ID: <DB0A6EBA-A789-4F07-BAF0-F2C1872EAAA4@benramsey.com>
Content-Type: multipart/signed;
	boundary="Apple-Mail=_02EAA385-4C38-431D-B039-F0503924BD7D";
	protocol="application/pgp-signature";
	micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Fri, 8 May 2020 01:20:53 -0500
In-Reply-To: <05D65F68-662F-4AE4-8D84-25B1D4279420@newclarity.net>
Cc: Dan Ackroyd <Danack@basereality.com>,
 Rowan Tommins <rowan.collins@gmail.com>,
 PHP internals <internals@lists.php.net>,
 Larry Garfield <larry@garfieldtech.com>
To: Mike Schinkel <mike@newclarity.net>
References: <05D65F68-662F-4AE4-8D84-25B1D4279420@newclarity.net>
Subject: Re: A Standard PHAR library included with PHP?
From: ben@benramsey.com (Ben Ramsey)

--Apple-Mail=_02EAA385-4C38-431D-B039-F0503924BD7D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On May 7, 2020, at 21:02, Mike Schinkel <mike@newclarity.net> wrote:
>=20
> 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=E2=80=99s 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=E2=80=99t 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 =E2=80=9Cstarts =
up=E2=80=9D).

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

--Apple-Mail=_02EAA385-4C38-431D-B039-F0503924BD7D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iHUEAREIAB0WIQToXQMR3fpbrPOmEOewLZeYnIwHGwUCXrT6RQAKCRCwLZeYnIwH
G2PRAPsHSJEPmW5ggju+sveKuTDaLLenMaOh8DZvFwtfxX61SAEAgIBKxsG77149
3MKDgD64C0wPRkbzWnwln1T317KU4Bo=
=yL8t
-----END PGP SIGNATURE-----

--Apple-Mail=_02EAA385-4C38-431D-B039-F0503924BD7D--