Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86839 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62100 invoked from network); 24 Jun 2015 10:05:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jun 2015 10:05:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.223.169 as permitted sender) X-PHP-List-Original-Sender: dmitry@zend.com X-Host-Fingerprint: 209.85.223.169 mail-ie0-f169.google.com Received: from [209.85.223.169] ([209.85.223.169:35511] helo=mail-ie0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B6/F0-55790-FC08A855 for ; Wed, 24 Jun 2015 06:05:04 -0400 Received: by iebrt9 with SMTP id rt9so29830753ieb.2 for ; Wed, 24 Jun 2015 03:05:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=D8YSSQzRpQLmb/MKGqto2BKoLoLvUaWp45FykfcfWH8=; b=ec/zmtQ97Sgr6lHVkPQopP0pJXlcTqqFLhDZxiRhpaNkbuXlQM6YgNdJymdSCYP1ea UxWmfK5XFyUgnAJHYOPtkki5rxjEtZ0TpkDPMbIriDXrzjWVQ8oxPs0c4b/rSnC/ECBh P+R0IbQZZISc3vQMURJPMwS01ocEL9Jl1sVL77j3ric0j/FiP+3pMw4FLnHTmAPoy2tC KitIc4eOPGcxcUH6fpf5zckw0O7a47/T01qx4EzYzbvqOuk8pi9ze74hUVKFX/Nju1wz r9gvEeSH3qXSlzP+QrtFvCv+0s8c9ShQDBCI5czEVUo+i738E7+UthD31qaT9/xnC1Nd fDtg== X-Gm-Message-State: ALoCoQkgyzGn+QkXx0HSDPDuy2ECR77TgrVe9s9iyuBN7RMTAMDpj1D+ZsIaPCn3q6r3y9+8nMwyM9Dz/HKir69a97u+LHTktN7eqGWyo2z/INQd1xJEULiHiN2Nq1R1zhXCJ2HvUDOSU1B9CY8I3gIcNDtHdLCMxC54RnD8KedXrXluSECnz8U= MIME-Version: 1.0 X-Received: by 10.50.138.136 with SMTP id qq8mr2076845igb.27.1435140299915; Wed, 24 Jun 2015 03:04:59 -0700 (PDT) Received: by 10.50.51.161 with HTTP; Wed, 24 Jun 2015 03:04:59 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Jun 2015 13:04:59 +0300 Message-ID: To: Ferenc Kovacs Cc: Yasuo Ohgaki , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e0111be1cc7a827051940a318 Subject: Re: [PHP-DEV] Move to Fast ZPP? From: dmitry@zend.com (Dmitry Stogov) --089e0111be1cc7a827051940a318 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable We should NOT use it everywhere. It'll lead to code bloat. Thanks. Dmitry. On Wed, Jun 24, 2015 at 12:21 PM, Ferenc Kovacs wrote: > On Wed, Jun 24, 2015 at 3:42 AM, Yasuo Ohgaki 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 > > 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_ZP= P) > > > > > > 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? > > -- > Ferenc Kov=C3=A1cs > @Tyr43l - http://tyrael.hu > --089e0111be1cc7a827051940a318--