Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75761
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.178 as permitted sender)
References: <b39ebab3d19d76cda9bafa25919c0e67@mail.gmail.com>
 <CAEZPtU52X737iUZgKUJbT0bb9z-cr_EYfxMcmv804AhnTpLnhg@mail.gmail.com>
 <CAMUwpuQrQd-ROPN0oRk37+U1JFnz487__vZxGjSC5f-TcYyfqg@mail.gmail.com>
 <2de3e71e35addbf16b2dc622f4c81eff@mail.gmail.com> <53CCD9BB.6060108@php.net> <53CCE669.8080403@beccati.com>
In-Reply-To: <53CCE669.8080403@beccati.com>
MIME-Version: 1.0
Thread-Index: AQI8QOdx/Do9KUTbDGI5HWlFNEg77gG/yJdxAZUjVGUDCtHniQEU+gxPAeJu+omahlzzkA==
Date: Mon, 21 Jul 2014 13:16:16 +0300
Message-ID: <c3cc43db4529cf076310f482d80bb7ab@mail.gmail.com>
To: Matteo Beccati <php@beccati.com>, internals@lists.php.net
Cc: Sebastian Bergmann <sebastian@php.net>
Content-Type: text/plain; charset=UTF-8
Subject: RE: [PHP-DEV] RFC: Move phpng to master
From: zeev@zend.com (Zeev Suraski)

> -----Original Message-----
> From: Matteo Beccati [mailto:php@beccati.com]
> Sent: Monday, July 21, 2014 1:08 PM
> To: internals@lists.php.net
> Cc: Sebastian Bergmann
> Subject: Re: [PHP-DEV] RFC: Move phpng to master
>
> To be honest I don't think we're anywhere near the point where it's safe
> to
> merge phpng to master.

Why?  People aren't supposed to run production or even development code
initially from master.

I don't know how many people here were around when PHP 5, 4 and 3 came to
be - but when you're dealing with a major version with such massive code
changes, you don't get everything right in day one.  It will require a
community effort - which is exactly what we're trying to achieve here.  I
don't think that community effort will happen if we don't move it to master
and give developers the needed clarity and motivation to work on this.

> Also, one thing that might have been overlooked is that merging phpng to
> master would completely bypass the voting phase on
> https://wiki.php.net/rfc/fast_zpp

Our thinking is to use this only for performance sensitive functions that
actually move the needle, as opposed to using it across the board - which
was the original thinking behind the fast_zpp API.  Fast_zpp for this
limited set of functions is now a part of phpng;  We can decide whether or
not we revisit the proposal for using fast_zpp more widely, although as I
said in the past, I'm not too fond of the new macro-based APIs myself.  For
performance sensitive functions that are used a lot, though, I think it
makes perfect sense.

Zeev