Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74482 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86070 invoked from network); 26 May 2014 07:17:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 May 2014 07:17:39 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain zend.com from 209.85.220.172 cause and error) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.220.172 mail-vc0-f172.google.com Received: from [209.85.220.172] ([209.85.220.172:61821] helo=mail-vc0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A2/E3-60353-09AE2835 for ; Mon, 26 May 2014 03:17:37 -0400 Received: by mail-vc0-f172.google.com with SMTP id ik5so5482273vcb.3 for ; Mon, 26 May 2014 00:17:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=bRMdwapy96Sb4pBNwp49O0Xpth4v4tFgr4HpRk1AtRg=; b=lE/7+/X9h3SdYVtVaQFxW7sBwVXsrCR8/q6z3k6WBuEl+wyP9JcxFH3GY3pSiU9tYX Ygihx0nPSocWgPOJL895CuD33z7+CmUzsQXIaLj6MBPO/RdjNaxJL+ODAkYI3ssYSEND Tqaxy8UJoer3NIFVveWgiZ6ItpBN/Zno2cnnuXdXGwB2MexVpZn97Emsrwyus13TqS58 /CAvn1m0lK1AyYXKtBE24YGaRJhlZZ6HZgTx2Jr8n9uc6nC53Calvy112y022iNb0iyP Mxkp80lYgd3lMpSUstpNUcrKyIHJRcoBFFwixGxDmVV5+atnlWdscYcuW7jfDZf98efy XA6g== X-Gm-Message-State: ALoCoQldP6ri/y0YPQUw1baS6cHibXxuY1IY0BS3WxWIc5I37k69fy17BFWiHwnuB+x+u5A/+R/2Y3jjmJLhE4Vt/c5YRHo/kYOHkj8j33C2FbAcXcwGHR8kT3IPQGmMgblMp6rSoYc7 X-Received: by 10.58.198.107 with SMTP id jb11mr20077839vec.10.1401088653406; Mon, 26 May 2014 00:17:33 -0700 (PDT) References: <-6285448086228171932@unknownmsgid> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQLISQrsk8i2VcNg8ucmWRPPETiFcgJicTjAAZQK7DoBczRyxQGdUXOimSiZNnA= Date: Mon, 26 May 2014 10:17:32 +0300 Message-ID: <67d97efff27b61e45ef74d4f4339b4b3@mail.gmail.com> To: Dmitry Stogov Cc: Xinchen Hui , PHP Internals , Bob Weinand , Stas Malyshev , Andi Gutmans , Nikita Popov Content-Type: multipart/alternative; boundary=047d7b6dc67a7c4de104fa485f99 Subject: RE: [RFC] Fast Parameter Parsing API From: zeev@zend.com (Zeev Suraski) --047d7b6dc67a7c4de104fa485f99 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I think the main challenge is the fact it turns what today is a one-liner (albeit a bit obscure) into a long multi-line all-caps gig. I=E2=80=99ve = tried to think about alternatives but so far came short with something that elegantly solves the problem, short of using C++ which I think goes too far in the context of what we=E2=80=99re trying to achieve. I=E2=80=99ll do some more thinking=E2=80=A6 Zeev *From:* Dmitry Stogov [mailto:dmitry@zend.com] *Sent:* Monday, May 26, 2014 10:10 AM *To:* Zeev Suraski *Cc:* Xinchen Hui; PHP Internals; Bob Weinand; Stas Malyshev; Andi Gutmans; Nikita Popov *Subject:* Re: [RFC] Fast Parameter Parsing API I personally see it more readable than "sZ|l", but of course, other people may think differently. I would be glad if someone would propose something useful in reasonable time. Thanks. Dmitry. On Mon, May 26, 2014 at 11:01 AM, Zeev Suraski wrote: To be perfectly honest, I tend to agree that the readability issues with this proposal make it a bit difficult to digest. And I'm not taking a 2.5% real world performance gain lightly - it's huge. I think we need to consider other alternatives as code readability and maintainability are important factors to consider, not just performance... Zeev On 26 =D7=91=D7=9E=D7=90=D7=99 2014, at 08:39, Dmitry Stogov wrote: I would be glad to see proposals from Hannes and Johannes, but we also need to move phpng forward, and I wouldn't like to spend on this too much time. Our proposal is mainly about speed (as well as the main phpng goal). We identified yet another bottleneck and eliminated it. Changes in readability and compile-time type checking are side effects of implementation. Thanks. Dmitry. On Sat, May 24, 2014 at 4:50 PM, Xinchen Hui wrote: Hey: On Fri, May 23, 2014 at 7:36 PM, Dmitry Stogov wrote: > Please take a look at https://wiki.php.net/rfc/fast_zpp It's really a great improvement. zend_parse_parameters is too heavy, and to me: Z_PARAM_STR() is obviously readable than zend_parse_parameter("s" /* what the hell s means here? */,) and the performance gain is also very significant .. actually, I thought about somethings like that.. but this patch is better... and these new APIs didn't break any APIS, just provides a more fast choice... I really don't understand why you guys think it not good? thanks > > Thanks. Dmitry. -- Xinchen Hui Laruence Consultant at Zend http://www.laruence.com/ --047d7b6dc67a7c4de104fa485f99--