On Mon, Nov 16, 2015 at 12:13 PM, Jefferson Gonzalez wrote:
> On 11/14/2015 08:03 PM, Rasmus Lerdorf wrote:
>>
>> Beyond that I can't picture what possible use this could be.
>
>
> I also think that the ability to have a .phpc and .php side by side would be
> nice, but not for hiding the source co
On 11/16/2015 03:13 PM, Jefferson Gonzalez wrote:
> On 11/14/2015 08:03 PM, Rasmus Lerdorf wrote:
>> Beyond that I can't picture what possible use this could be.
>
> I also think that the ability to have a .phpc and .php side by side
> would be nice, but not for hiding the source code. It would be
On 11/14/2015 08:03 PM, Rasmus Lerdorf wrote:
Beyond that I can't picture what possible use this could be.
I also think that the ability to have a .phpc and .php side by side
would be nice, but not for hiding the source code. It would be useful
especially for php-cgi and secondary for php-cli
On Nov 13, 2015, at 21:32, Stephen Coakley wrote:
>
>> On 11/13/2015 05:46 PM, Rasmus Lerdorf wrote:
>>> On Nov 13, 2015, at 17:00, Stephen Coakley wrote:
>>>
> On 11/13/2015 03:45 PM, Sebastian Bergmann wrote:
> On 11/13/2015 04:35 PM, Stephen Coakley wrote:
> This is quite similar
Hi Stephen,
Le 13/11/2015 22:35, Stephen Coakley a écrit :
Hello all,
I've been thinking about PHP optimization and distribution, and I
would like to hear some opinions on introducing a new feature for a
future PHP 7 version. Here's the concept: allow PHP opcode to be both
saved after parsin
On Fri, Nov 13, 2015 at 1:35 PM, Stephen Coakley
wrote:
> I've been thinking about PHP optimization and distribution, and I would like
> to hear some opinions on introducing a new feature for a future PHP 7
> version. Here's the concept: allow PHP opcode to be both saved after parsing
> a file, a
On 11/13/2015 05:46 PM, Rasmus Lerdorf wrote:
On Nov 13, 2015, at 17:00, Stephen Coakley wrote:
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 f
On Nov 13, 2015, at 17:00, Stephen Coakley wrote:
>
>> 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
>
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
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,
Hello all,
I've been thinking about PHP optimization and distribution, and I would
like to hear some opinions on introducing a new feature for a future PHP
7 version. Here's the concept: allow PHP opcode to be both saved after
parsing a file, and to be loaded and executed, similar to the bcomp
11 matches
Mail list logo
