Re: [PHP-DEV] RFC: Removing the Zend API

2009-04-06 Thread Rob Nicholson
Paul Biggar paul.big...@gmail.com wrote on 31/03/2009 00:06:33: I've added a new RFC to the wiki (http://wiki.php.net/rfc/remove_zend_api). It details a plan to try and decouple the Zend engine from the libraries, in order to allow large scale changes to the Zend engine in the future. The

Re: [PHP-DEV] RFC: Removing the Zend API

2009-04-05 Thread Paul Biggar
Hi Andi, On Wed, Apr 1, 2009 at 3:35 PM, Andi Gutmans a...@zend.com wrote: Hi Paul, This is something I have considered in the past esp. as it would also reduce dependency of extensions on PHP runtime and make it easier for 3rd parties to distribute PHP extensions which don't have to be

Re: [PHP-DEV] RFC: Removing the Zend API

2009-04-02 Thread Paul Biggar
2009/4/1 Johannes Schlüter johan...@schlueters.de: Hi, On Wed, 2009-04-01 at 16:16 +0100, Paul Biggar wrote: I think that to handle more complex cases we need the kind of information which makes it straightforward to easily generate code to make a seamless interface between C and the engine

Re: [PHP-DEV] RFC: Removing the Zend API

2009-04-01 Thread Paul Biggar
On Tue, Mar 31, 2009 at 9:23 PM, Nuno Lopes nlop...@php.net wrote: Hi Paul et all, I fully understand (and even share) your motivations and goals. However it seems to me that describing an extension in PHP will lead to loss of performance, as you cannot capture certain C features in PHP. For

Re: [PHP-DEV] RFC: Removing the Zend API

2009-04-01 Thread Johannes Schlüter
Hi, On Wed, 2009-04-01 at 14:24 +0100, Paul Biggar wrote: Moreover, in your example in the wiki you don't include how you would do parameter parsing. Or do you rely on the code generator to look at the C functions signatures and figure out by itself what to do? (actually there is some

RE: [PHP-DEV] RFC: Removing the Zend API

2009-04-01 Thread Andi Gutmans
Hi Paul, This is something I have considered in the past esp. as it would also reduce dependency of extensions on PHP runtime and make it easier for 3rd parties to distribute PHP extensions which don't have to be rebuilt per-PHP version. This is similar to JNI. There are some real challenges

Re: [PHP-DEV] RFC: Removing the Zend API

2009-04-01 Thread Paul Biggar
2009/4/1 Johannes Schlüter johan...@schlueters.de: Hi, On Wed, 2009-04-01 at 14:24 +0100, Paul Biggar wrote: Moreover, in your example in the wiki you don't include how you would do parameter parsing. Or do you rely on the code generator to look at the C functions signatures and figure

Re: [PHP-DEV] RFC: Removing the Zend API

2009-04-01 Thread Paul Biggar
On Wed, Apr 1, 2009 at 3:35 PM, Andi Gutmans a...@zend.com wrote: Hi Paul, This is something I have considered in the past esp. as it would also reduce dependency of extensions on PHP runtime and make it easier for 3rd parties to distribute PHP extensions which don't have to be rebuilt

Re: [PHP-DEV] RFC: Removing the Zend API

2009-04-01 Thread Johannes Schlüter
Hi, On Wed, 2009-04-01 at 16:16 +0100, Paul Biggar wrote: I think that to handle more complex cases we need the kind of information which makes it straightforward to easily generate code to make a seamless interface between C and the engine API. The only case I had thought of was to somehow

Re: [PHP-DEV] RFC: Removing the Zend API

2009-03-31 Thread Nuno Lopes
Hi Paul et all, I fully understand (and even share) your motivations and goals. However it seems to me that describing an extension in PHP will lead to loss of performance, as you cannot capture certain C features in PHP. For example, there are some internal functions that rely on pointer