Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49157
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.183 as permitted sender)
Message-ID: <4C50D6FA.40404@sugarcrm.com>
Date: Wed, 28 Jul 2010 18:18:50 -0700
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: Jonathan Bond-Caron <jbondc@openmv.com>
CC: "internals@lists.php.net" <internals@lists.php.net>
References: <001e01cb2eb8$a0928c50$e1b7a4f0$@com>
In-Reply-To: <001e01cb2eb8$a0928c50$e1b7a4f0$@com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Zend Extension - zend_compile_file - interoperability?
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

> I've starting playing around with the zend engine,
>
> is there any hope / plans  for better interoperability with how
> zend_compile_file() should be extended?
>
> The goal being to reduce the amount of  "X is not compatible with Y".

In most cases, overriding zend_compile_file() and calling previous 
handler should be enough. If it doesn't work of soe special 
modifications then additional handlers might not help either. 
Compatibility problems can arise from something like extension X (e.g. 
bytecode cache) expects certain structures to reside in shared memory 
for performance reasons while extension Y modifying them since it 
doesn't know anything about extension X.

> # Bytecode loaders / optimizers / dumpers (zend optimizer, ioncube loader,
> vld, etc.)

Those should use other handlers, such as op array ctor/dtor/handler.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227