Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89210
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <77.62.62946.F6D56465@pb1.pair.com>
To: internals@lists.php.net
References: <12.A1.62946.CB756465@pb1.pair.com> <564659DF.5070904@php.net>
Date: Fri, 13 Nov 2015 16:00:12 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <564659DF.5070904@php.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Support for writing and executing compiled opcode
From: me@stephencoakley.com (Stephen Coakley)

On 11/13/2015 03:45 PM, Sebastian Bergmann wrote:
> On 11/13/2015 04:35 PM, Stephen Coakley wrote:
>> This is quite similar to Python's ability to execute Python scripts
>> compiled to bytecode as *.pyc files. The feature has seen great
>> success in
>> Python, mostly for distributing releases of software or deploying to a
>> server.
>
>   Correct me if I'm wrong, but this should already be possible with OpCache
>   and its filesystem backend in PHP 7.0.
>
>   See http://talks.php.net/froscon15#/php7pcache1 and following for
>   details.

That's great! That's about halfway toward what I'm looking for. That 
means that the engine is likely already capable of doing these things -- 
the next step is to be able to execute any given .php.bin file like in 
that talk. The idea would be to be able to bypass the caching mentality 
by executing an already compiled file, instead of checking if the 
original .php file has a corresponding bin file in the cache

-- 
Stephen