Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110097
Message-ID: <15BDA2A4-4654-46D9-BEA9-83E7515A25F6@benramsey.com>
Content-Type: multipart/signed;
	boundary="Apple-Mail=_A65404FE-BC0B-4AA9-B398-3D87E807852D";
	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 17:29:24 -0500
In-Reply-To: <004e01d62574$aece7b90$0c6b72b0$@jhdxr.com>
Cc: Mike Schinkel <mike@newclarity.net>,
 Dan Ackroyd <Danack@basereality.com>,
 Rowan Tommins <rowan.collins@gmail.com>,
 PHP internals <internals@lists.php.net>
To: CHU Zhaowei <me@jhdxr.com>
References: <05D65F68-662F-4AE4-8D84-25B1D4279420@newclarity.net>
 <004e01d62574$aece7b90$0c6b72b0$@jhdxr.com>
Subject: Re: [PHP-DEV] A Standard PHAR library included with PHP?
From: ben@benramsey.com (Ben Ramsey)

--Apple-Mail=_A65404FE-BC0B-4AA9-B398-3D87E807852D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On May 8, 2020, at 15:10, CHU Zhaowei <me@jhdxr.com> wrote:
>=20
> This idea has been brought up during the RFC for preloading. I think =
it's a good idea because it will make the c part smaller, and reduce the =
cost of maintenance. The question is,  where should we start with? the =
existing functions in C work well,  why should we put effect to convert =
them back to php. For new functions, it means more workload. The RFC's =
author has to convince others that this feature is better to implement =
in PHP rather than in C.


I agree that the RFC for this must make a compelling case for it, since =
it will require work in the core to make this possible, and that work =
probably won=E2=80=99t be trivial.

As for porting code from C into PHP, I don=E2=80=99t think it has to be =
done en masse. I would start with no more than a handful of simple =
functions (maybe even `uniqid()`, since that=E2=80=99s where this =
discussion began) that would act as examples.

Once the capability for this is implemented and shipped, I think finding =
contributors to port functionality on a function-by-function basis =
won=E2=80=99t be difficult, since more folks in the community will be =
able to contribute, but it also doesn=E2=80=99t need to be done at a =
rapid pace, either. The primary benefit of porting from C to PHP in the =
core, IMO, is for greater opportunities for contributions and =
maintenance from the community.

Cheers,
Ben


--Apple-Mail=_A65404FE-BC0B-4AA9-B398-3D87E807852D
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-----

iHUEAREIAB0WIQToXQMR3fpbrPOmEOewLZeYnIwHGwUCXrXdRAAKCRCwLZeYnIwH
G2XCAQCQag8/kpWXmPL3EPMcrPxUl+8KaObYNCl52acQHi9a/wD+P/NsS8elOPRP
g3tzqk5qHlzuAK8zQATI+2kx3FA6jAA=
=d4vw
-----END PGP SIGNATURE-----

--Apple-Mail=_A65404FE-BC0B-4AA9-B398-3D87E807852D--