Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99403
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain birkholz.biz designates 144.76.185.232 as permitted sender)
To: internals@lists.php.net
References: <5313411f-40b4-58c6-83a8-7e813526f2a7@tekwire.net>
 <CAF+90c9j4c+L8irb+tN+Qcx7SxA-d1EMBrXuZGw3FXi2SZr-Jw@mail.gmail.com>
Message-ID: <cc8a057b-c46b-6580-0344-60fc3f3dfd92@birkholz.biz>
Date: Tue, 6 Jun 2017 17:52:14 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c9j4c+L8irb+tN+Qcx7SxA-d1EMBrXuZGw3FXi2SZr-Jw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Proposing inclusion of PCS in the 7.2 core distribution
From: php@dennis.birkholz.biz (Dennis Birkholz)

Hi together,

Am 06.06.2017 um 14:43 schrieb Nikita Popov:
> First of all: I think the ability to implement parts of PHP extensions in
> PHP is extremely important and will be a game changer in our ability to
> maintain and improve our standard library.

I agree with you here 100%.

> 1. As far as I understand, PCS relies on autoloading. There are two issues
> here: First, autoloading does not register symbols prior to autoloading.
> This means that functions like get_defined_classes() will not behave as
> expected. Second, autoloading does not support functions. I think both of
> these problems can be solved with some up-front symbol analysis. Lazily
> compiling internal functions should not run into any of the problems we
> have with userland function autoloading.

(disclaimer: I have not deep knowledge how the core really works)

From what I see there is a difference between writing extension code in
PHP and placing that plain PHP files somewhere when installing. So I
would argue when compiling the extension or the core, all these PHP
extension stuff should get compiled to OpCodes and put in a segment of
the resulting binary.
The OpCache could then be modified to allow it to use the OpCodes from
these read-only segments (one for the core, one optionally for each
extension). That would void the problems you mentioned above, but maybe
I am missing how the OpCache and symbol registration work in PHP.

Greets
Dennis