Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86838
Return-Path: <tyra3l@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 57157 invoked from network); 24 Jun 2015 09:21:16 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 24 Jun 2015 09:21:16 -0000
Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.181 as permitted sender)
X-PHP-List-Original-Sender: tyra3l@gmail.com
X-Host-Fingerprint: 209.85.217.181 mail-lb0-f181.google.com  
Received: from [209.85.217.181] ([209.85.217.181:35386] helo=mail-lb0-f181.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id FD/10-55790-8867A855 for <internals@lists.php.net>; Wed, 24 Jun 2015 05:21:14 -0400
Received: by lbbwc1 with SMTP id wc1so22535096lbb.2
        for <internals@lists.php.net>; Wed, 24 Jun 2015 02:21:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=3kwNeEb0bFPr8+d0fD83btC5led/xQOWcxPKSST3qys=;
        b=Z+a9C4GoBSCxPhMhl7TwDr/WfBWjUYLZ+EGOjk+tCg6TCSASjaiD7lh64B33jUT8iH
         xiZysqPdRL+bXH2OBRBK6HIYY6USmYAzStxLF2BbE4ZVvLC7Ku9f7FQsLYp8yoGHBsVG
         MuPRSKo5vvspUpIPX5/SNXrrrAb7px7LFy1ohn7CZqfKiuNEfDBb/iP+J6aigBqy2cNe
         00FyDKvrBJHYPkOsttpOQYccIUNnnFz9EEQ91w49S+GnSYQzLPi1OgBXYhm//Tai/5Mz
         gvprw8ZwZUGB2jPZbiwvIF3dFk4Zgz4/PXZiUNNvw1ATCg9qkhyNZwidZMD/ZogJiRJy
         P6lw==
MIME-Version: 1.0
X-Received: by 10.112.154.71 with SMTP id vm7mr38279113lbb.96.1435137669596;
 Wed, 24 Jun 2015 02:21:09 -0700 (PDT)
Received: by 10.152.43.105 with HTTP; Wed, 24 Jun 2015 02:21:09 -0700 (PDT)
In-Reply-To: <CAGa2bXY1hKW3qX3jBwKge7RDihS6TjxAW3p+-kKRiW4OmePLSQ@mail.gmail.com>
References: <CAGa2bXY1hKW3qX3jBwKge7RDihS6TjxAW3p+-kKRiW4OmePLSQ@mail.gmail.com>
Date: Wed, 24 Jun 2015 11:21:09 +0200
Message-ID: <CAH-PCH6YtrM8B1DBWXL7+5mfgUROKKwqFd2VDL+FZtUEfRpREw@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01227ec0001f64051940076f
Subject: Re: [PHP-DEV] Move to Fast ZPP?
From: tyra3l@gmail.com (Ferenc Kovacs)

--089e01227ec0001f64051940076f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 24, 2015 at 3:42 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:

> 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
>

it was meant as a performance optimization for the most heavy/hot codepaths=
.
What gave you the idea that the situation changed and we should use it
everywhere?

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--089e01227ec0001f64051940076f--