Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75753
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAMUwpuQrQd-ROPN0oRk37+U1JFnz487__vZxGjSC5f-TcYyfqg@mail.gmail.com>
References: <b39ebab3d19d76cda9bafa25919c0e67@mail.gmail.com>
	<CAEZPtU52X737iUZgKUJbT0bb9z-cr_EYfxMcmv804AhnTpLnhg@mail.gmail.com>
	<CAMUwpuQrQd-ROPN0oRk37+U1JFnz487__vZxGjSC5f-TcYyfqg@mail.gmail.com>
Date: Mon, 21 Jul 2014 13:27:57 +0400
Message-ID: <CA+9eiLs3=5CF=KO7Fi28L1S1R833ZGXf0Wfr9gRZO6mCYzRamQ@mail.gmail.com>
To: Julien Pauli <jpauli@php.net>
Cc: Pierre Joye <pierre.php@gmail.com>, Zeev Suraski <zeev@zend.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0158b2f6ee92d104feb0b8a4
Subject: Re: [PHP-DEV] RFC: Move phpng to master
From: dmitry@zend.com (Dmitry Stogov)

--089e0158b2f6ee92d104feb0b8a4
Content-Type: text/plain; charset=UTF-8

Hi Julien,


> Hi
>
> I can only agree here.
>
> I'd like a clean API. We need to consider PHP-Next jump as an opportunity
> to
> clean our API and finally have something understandable for a
> newcomer, and documented. That's a move nobody dared to take in the
> last decade, degrading more and more our codebase in term of
> understandability and flexibility. This can't last
>

I'm more than agree about internal cleanup.
phpng benchmark results proved that we take the right direction and now we
implemented most the ideas we had.
Note that we tried not to change PHP behaviour in any way.
Now it's a good time to start the cleanup work.


> Old features and unused things should be cleaned up.
> Quickly caught, impacting the engine :
> - Resources are a hell, mixed with zend_lists etc... inconsitstent and
> absolutely PITA to develop with.
> - Streams need to be cleaned up and reworked to support full
> asynchronous IOs, which could involve threads, thus engine tied
> - Signals have been worked on starting with 5.4 (AFAIR), but never
> activated by default. I guess the actual implementation lacks a bit
> more reflection to be stable, and to finally propose signal managers
> into userland. ext/pcntl should be somehow merged to core, and this as
> well would involve engine work
> - TSRM need to find love, or to find a better replacement, which would
> involve a big engine work as well
> - ... and so on
>

Some of the topics above are really big... :)


>
> Macro hell should be reworked as inlined functions, and I'd like we
> start supporting C99 as well.
>
> Performance is a userland point.
> API, doc, and clean things are developers points, and IMO, they are as
> important.
>
> What about merging OPCache to the branch ?
> This was talked about at PHP5.5 release, has never happened yet, and
> doesn't seem planed. This could have a big impact on the engine
> codebase.
>

What do you mean? isn't it already there.
I'm also going to remove opcache code for old PHP versions in php-next.


> I just cant believe we won't rework our API , fully and deeply, for
> PHP-Next.
>

You and others are welcome. Once we merge phpng into master, we all may
cooperate better.

Thanks. Dmitry.


>
> Julien
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--089e0158b2f6ee92d104feb0b8a4--