Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76034
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CA+9eiLtYT_DSE1yu2KEWiHc=AVbG0WXYCUQBBcvWp6=RyNA=WQ@mail.gmail.com>
References: <b39ebab3d19d76cda9bafa25919c0e67@mail.gmail.com>
	<53CF4146.5080800@sugarcrm.com>
	<ea7a80e05193b8a055747d8cee88a45f@mail.gmail.com>
	<CA+9eiLtYT_DSE1yu2KEWiHc=AVbG0WXYCUQBBcvWp6=RyNA=WQ@mail.gmail.com>
Date: Thu, 24 Jul 2014 23:06:07 +0400
Message-ID: <CA+9eiLshuogpuJVzPkuemFA=jW47EOwCfZLkySNao=D4CtgGHA@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec52d571932131804fef526c7
Subject: Re: [PHP-DEV] RFC: Move phpng to master
From: dmitry@zend.com (Dmitry Stogov)

--bcaec52d571932131804fef526c7
Content-Type: text/plain; charset=UTF-8

The "the" before "start" is a mistake :)


On Thu, Jul 24, 2014 at 11:04 PM, Dmitry Stogov <dmitry@zend.com> wrote:

> Hi,
>
> I didn't see any phpng related discussion for a day.
> If we have nothing to discuss, may be we should just the start a voting
> process. :)
>
> It's not a problem for me to wait a week or even month. I just like to
> know. if anyone thinks, that we have any stoppers to start the voting.
>
> Last days we tried to improve https://wiki.php.net/phpng-upgrading
> However, our English is poor and boring. It would be cool, if native
> speakers would improve the docs. (section related to Objects is not ready
> yet).
>
> Thanks. Dmitry.
>
>
>
> On Thu, Jul 24, 2014 at 12:27 AM, Zeev Suraski <zeev@zend.com> wrote:
>
>> > -----Original Message-----
>> > From: Stas Malyshev [mailto:smalyshev@sugarcrm.com]
>> > Sent: Wednesday, July 23, 2014 8:00 AM
>> > To: Zeev Suraski; PHP internals
>> > Subject: Re: [PHP-DEV] RFC: Move phpng to master
>> >
>> > 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.
>>
>> As Dmitry mentioned, this is something we're going to work on (with
>> primary
>> focus around the porting guide, and secondary focus on extending the
>> internals document).
>>
>> Zeev
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>

--bcaec52d571932131804fef526c7--