Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66345 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59094 invoked from network); 28 Feb 2013 19:13:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Feb 2013 19:13:57 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.139 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.139 smtp139.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.139] ([67.192.241.139:39901] helo=smtp139.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CF/66-25879-47CAF215 for ; Thu, 28 Feb 2013 14:13:56 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp30.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 9A565349876; Thu, 28 Feb 2013 14:13:53 -0500 (EST) X-Virus-Scanned: OK Received: by smtp30.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 51243349864; Thu, 28 Feb 2013 14:13:53 -0500 (EST) Message-ID: <512FAC72.9000808@sugarcrm.com> Date: Thu, 28 Feb 2013 11:13:54 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: Nikita Popov CC: PHP Developers Mailing List References: <435a322ccb14090d3bcf6bf8a110396d@mail.gmail.com> <3206872690693024300@unknownmsgid> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > It's not a syntax change, but it is a very, very large engine change. Yes, > it does not touch the Zend engine itself, but it adds a large amount of new > code that is close to the engine. People doing engine changes will need to > modify it too (thus it is quasi part of the engine, even if it lives in a I'm not sure how it makes sense - people changing the engine had to modify SPL or libxml or SOAP extension, for example - so now SOAP is part of the engine? Since engine is underlying API, if you modify the engine then you may have to modify extensions, doesn't mean all extensions are part of the engine. I find this pretty strained argument. > separate directory). All existing core devs will have to study and > understand the code. All new developers have an additional piece of very > complex code to study before they can start making core changes. Again, by this logic everything is the engine - if you didn't look at how PDO works and changed the engine in a way that broke PDO - it's bad, so by that logic PDO is the engine. And so is pretty much any extension anybody cares about. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227