Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66351 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67958 invoked from network); 28 Feb 2013 19:27:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Feb 2013 19:27:11 -0000 Authentication-Results: pb1.pair.com header.from=nikita.ppv@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=nikita.ppv@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.52 as permitted sender) X-PHP-List-Original-Sender: nikita.ppv@gmail.com X-Host-Fingerprint: 209.85.219.52 mail-oa0-f52.google.com Received: from [209.85.219.52] ([209.85.219.52:37502] helo=mail-oa0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 96/78-25879-D8FAF215 for ; Thu, 28 Feb 2013 14:27:09 -0500 Received: by mail-oa0-f52.google.com with SMTP id k14so4211118oag.25 for ; Thu, 28 Feb 2013 11:27:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=3T2iv1g0gB4Ra3o0ea16Z+vppr6wDwF8yHZKYx0P22w=; b=HnwT48n7w9OGPB9JHCZ3cK2EUV7ya/QmqpGOAp5dgX9hq8mdYPC4S8Y6rS/yx6gnWR on7aorcPhqxkoqlra08kllTgEoWe/8G6T1NYwbMu0rUWAvWa0806BnrP3k7Cnr8h+p8o jlbgUemRL2IbcLu3fqHcmfLeMqhEN0LvolvcNUCwPqPKvrIm2y6UoZ8DeVEEVgzWCW0l GZWoDgEegAvwQHVEAMPpLKGkF9+KnbtZABut5Q7RxXJn0pHZJ22+Y5TjWxbSOrMUvL4z CT9Q4CMKkgrF+xXU1inYOOGd5eZshkF+jjQvvYk9zt/0CSn0Ox2O+y7ZbDIXcsgoVf9N 52vg== MIME-Version: 1.0 X-Received: by 10.182.159.98 with SMTP id xb2mr6390288obb.81.1362079626929; Thu, 28 Feb 2013 11:27:06 -0800 (PST) Received: by 10.182.49.136 with HTTP; Thu, 28 Feb 2013 11:27:06 -0800 (PST) In-Reply-To: <512FAC72.9000808@sugarcrm.com> References: <435a322ccb14090d3bcf6bf8a110396d@mail.gmail.com> <3206872690693024300@unknownmsgid> <512FAC72.9000808@sugarcrm.com> Date: Thu, 28 Feb 2013 20:27:06 +0100 Message-ID: To: Stas Malyshev Cc: PHP Developers Mailing List Content-Type: multipart/alternative; boundary=14dae9399a4d51af9804d6cde049 Subject: Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution From: nikita.ppv@gmail.com (Nikita Popov) --14dae9399a4d51af9804d6cde049 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Feb 28, 2013 at 8:13 PM, Stas Malyshev wrote: > 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. > The difference between SOAP and ZO+ is the level of integration and dependency. If you do a change in the ZE there is a very high chance that you will not have to touch any code in SOAP, but you will quite likely need to adjust something in ZO+. Phar is the only of the current extensions that comes anywhere close to this. And ZO+ is still a *lot* more tightly integrated than Phar (and you know what a PITA Phar can be...) If you don't see that ZO+ is an extension that is very tightly integrated with the ZE and rather sensitive to change, then sorry, can't help you. To me this seems obvious. Nikita --14dae9399a4d51af9804d6cde049--