Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99428
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.192.175 cause and error)
MIME-Version: 1.0
In-Reply-To: <523cbe62-d237-955a-e11f-87abaacbb816@tekwire.net>
References: <5313411f-40b4-58c6-83a8-7e813526f2a7@tekwire.net> <523cbe62-d237-955a-e11f-87abaacbb816@tekwire.net>
Date: Wed, 7 Jun 2017 14:53:13 +0100
Message-ID: <CA+kxMuQZF-1rGFCHy3SJLRuBxrSjx7A+0fYLVkjDMO+wKWM+sw@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@tekwire.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] About PCS (was : Proposing inclusion of PCS in the 7.2
 core distribution)
From: danack@basereality.com (Dan Ackroyd)

Hi Francois,

I'm in favour of shipping PHP code as part of either PHP core, and for
extensions.

I would use this for Imagick. There are several 'helper' functions
that would make this library easier to use, that are trivial to write
in PHP, that are incredibly not trivial to write in C.

> Please give examples of core extensions that, in your opinion, are susceptible to be partially or fully converted to PHP.

Uh - I don't really agree that any existing core code should be
converted to PHP. If the code is already there and working as C code,
there are very few benefits converting it to PHP now. If we ever get
around to refactoring how strings are stored in PHP, it's at that
point that converting existing functionality to PHP code might be a
good idea.

> Suggestions to complement existing core extensions (like an additional curl OO layer) are welcome too.

If you want this RFC to pass, I'd strongly recommend having
conversations about adding those as separate RFCs, once the "having
PHP code distributed with PHP" RFC is passed as otherwise the
signal-to-noise ratios will be terrible.

cheers
Dan
Ack