Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75920 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63333 invoked from network); 23 Jul 2014 04:59:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jul 2014 04:59:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.67 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.67 smtp67.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.67] ([108.166.43.67:52234] helo=smtp67.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 49/FD-21666-7414FC35 for ; Wed, 23 Jul 2014 00:59:56 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp9.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id D5C393803F6; Wed, 23 Jul 2014 00:59:50 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp9.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 7B2EC38019A; Wed, 23 Jul 2014 00:59:50 -0400 (EDT) X-Sender-Id: smalyshev@sugarcrm.com Received: from Stass-MacBook-Pro.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net [108.66.6.48]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA) by 0.0.0.0:465 (trex/5.2.10); Wed, 23 Jul 2014 04:59:50 GMT Message-ID: <53CF4146.5080800@sugarcrm.com> Date: Tue, 22 Jul 2014 21:59:50 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Zeev Suraski , PHP internals References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] RFC: Move phpng to master From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > As we’re getting closer to release 5.6.0, and given the very high > level of interest in phpng, I think it’s time for us to provide some > clarity regarding what happens post 5.6.0. > > Dmitry and I wrote an RFC proposing that we merge phpng into master > and turn it into the basis of the next major version of PHP (name > TBD). I think before we do that we need to do much better documentation around the changes in the engine. I know that in the past we followed the "code is documentation" pattern, but the code there becomes more and more dense, with macros upon macros upon macros, and myriads of micro-optimizations which make sense only in specific context. Absent that context and documentation, understanding what is going on becomes much harder and so becomes dealing with that code. Some of the changes right now are partially documented in https://wiki.php.net/phpng-int, some (like parameter parsing API) not documented at all. Given that, I'm not even sure I understand what phpng is right now - as I didn't have time to parse every commit during active development. So it would be nice to have some internal docs if we want people to form an informed opinion about what is being proposed. And, of course, the porting guide for extension authors is another required part. I know the phpng team did great work porting the extensions, but people would need to support them and add the new ones, so it is a must. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/