Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43566 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68546 invoked from network); 31 Mar 2009 20:23:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Mar 2009 20:23:54 -0000 Authentication-Results: pb1.pair.com header.from=nlopess@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=nlopess@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.55.154.22 as permitted sender) X-PHP-List-Original-Sender: nlopess@php.net X-Host-Fingerprint: 212.55.154.22 relay2.ptmail.sapo.pt Linux 2.4/2.6 Received: from [212.55.154.22] ([212.55.154.22:54368] helo=sapo.pt) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0B/29-26784-8DB72D94 for ; Tue, 31 Mar 2009 15:23:54 -0500 Received: (qmail 25493 invoked from network); 31 Mar 2009 20:23:46 -0000 Received: from unknown (HELO sapo.pt) (10.134.37.163) by relay2 with SMTP; 31 Mar 2009 20:23:46 -0000 Received: (qmail 9202 invoked from network); 31 Mar 2009 20:23:46 -0000 X-AntiVirus: PTMail-AV 0.3-0.92.0 X-Virus-Status: Clean (0.00659 seconds) Received: from unknown (HELO PC3EE1F19287) (nunoplopes@sapo.pt@[93.197.130.121]) (envelope-sender ) by mta13 (qmail-ldap-1.03) with SMTP for ; 31 Mar 2009 20:23:46 -0000 Message-ID: <29CF2C07F9044405AF6332BE2F3A373F@PC3EE1F19287> To: "Paul Biggar" , "PHP Internals" References: Date: Tue, 31 Mar 2009 21:23:43 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Subject: Re: [PHP-DEV] RFC: Removing the Zend API From: nlopess@php.net ("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 arithmetic to get decent performance. Then you may extend to PHP to better capture these "dirty tricks", and then you'll end up with some DSL for building PHP extensions. It's not necessarily bad, it's just a lot of work.. :) 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 ambiguity, AFAIR, and thus guessing cannot be done reliably) To summarize my e-mail, I believe this is a very interesting idea, but needs a lot more thinking :) It's a nice SoC project nethertheless. Nuno ----- Original Message ----- > Hi, > > 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 RFC > describes a prototype phase of the project, which could reasonably be > done within a GSOC project, so I have added it to the GSOC 09 page > (http://wiki.php.net/gsoc/2009#prototyping_removal_of_the_zend_api). > > If anybody has any comments, I'd be delighted to hear them. If anybody > knows (or is) a good student looking for a GSOC project (and I've left > it late, there are only 3 days left to apply), please encourage the > student to look at this. Finally, if anybody is interested in helping > mentor this as part of the GSOC, I'd be grateful for the help (I have > to start writing my thesis soon). > > Thanks, > Paul