Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86826
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.53 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
Date: Wed, 24 Jun 2015 10:42:43 +0900
Message-ID: <CAGa2bXY1hKW3qX3jBwKge7RDihS6TjxAW3p+-kKRiW4OmePLSQ@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113937bcd6802e051939a162
Subject: Move to Fast ZPP?
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a113937bcd6802e051939a162
Content-Type: text/plain; charset=UTF-8

Hi all,

I'm wondering the state of Fast ZPP.
https://wiki.php.net/rfc/fast_zpp

Last year's Dmirty's commit message say, it should
only applied to most used functions due to the state of
Fast ZPP.

commit 27f38798a1963de1c60aae4ef8a3675138255574
Author: Dmitry Stogov <dmitry@zend.com>
Date:   Fri Jul 11 16:32:20 2014 +0400

    Fast parameter parsing API

    This API is experimental. It may be changed or removed.
    It should be used only for really often used functions.
    (Keep the original parsing code and wrap usage with #ifndef FAST_ZPP)


Are we supposed to convert anything to Fast ZPP now?
What about the  #ifndef FAST_ZPP? Is this required now?

BTW, if we are supposed to use only Fast ZPP,
https://github.com/php/php-src/blob/master/README.PARAMETER_PARSING_API
should be updated.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a113937bcd6802e051939a162--