Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74457 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95018 invoked from network); 23 May 2014 15:28:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 May 2014 15:28:25 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.47 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.192.47 mail-qg0-f47.google.com Received: from [209.85.192.47] ([209.85.192.47:60639] helo=mail-qg0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BE/D4-01753-8196F735 for ; Fri, 23 May 2014 11:28:24 -0400 Received: by mail-qg0-f47.google.com with SMTP id j107so8315610qga.34 for ; Fri, 23 May 2014 08:28:21 -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:content-transfer-encoding; bh=kvqu0BmYQVo8vUlv9JGvqi4CnVAukcu3BTPwq9HCnug=; b=j7W50SqhqmMz9rufhj4yfsuc2DGnA8qXBRBURNvLxy0MylDK9mfgWz8XOlo/O5j7J6 UGASF2IV8Er6bCL6GyQp3FllcglVhJQLaPLd48fBcZmF7PeeEPvy2TdHUyZLXCNT+O7g i15iU0cKFBVxF0oldR8Ask2upq/XN9Fox1CZLP+meTbMXgdZFcEFgj4oLA/7twHqWUDV 59VDpvGm+KQMJqdyi746uUVaMh9uEXNzjGauI7ChubdqQdmELIXVVlXh461DcstVCrV9 dWTv9l68bxhsRYCOWoSug3crX5PpqucM/XI8yNraLLTrTswtk0BX4r3PSbs+pchnq7+s WI7g== MIME-Version: 1.0 X-Received: by 10.140.101.99 with SMTP id t90mr7162750qge.115.1400858901245; Fri, 23 May 2014 08:28:21 -0700 (PDT) Received: by 10.140.47.231 with HTTP; Fri, 23 May 2014 08:28:21 -0700 (PDT) In-Reply-To: <1400851698.2870.9315.camel@guybrush> References: <79B69A20-15AD-4C07-B026-61C2C9DEBBE5@ajf.me> <1400851698.2870.9315.camel@guybrush> Date: Fri, 23 May 2014 17:28:21 +0200 Message-ID: To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= Cc: Andrea Faulds , Dmitry Stogov , PHP Internals , Bob Weinand , Stas Malyshev , Zeev Suraski , Xinchen Hui , Andi Gutmans , Nikita Popov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Fast Parameter Parsing API From: pierre.php@gmail.com (Pierre Joye) Hi Dmitry, Bob, On Fri, May 23, 2014 at 3:28 PM, Johannes Schl=C3=BCter wrote: > On Fri, 2014-05-23 at 13:52 +0100, Andrea Faulds wrote: >> On 23 May 2014, at 12:36, Dmitry Stogov wrote: >> >> > Please take a look at https://wiki.php.net/rfc/fast_zpp >> > >> > Thanks. Dmitry. >> >> This looks like a great idea. I like how it=E2=80=99s not only faster, b= ut it >> seems to be more readable. > > More readable? - I feel exactly the opposite. Yes, we get rid of void > pointers but use a pattern easy to understand. This looks like macro > hell. I feel the same way. I very much the idea of rewamping zpp, it is a long due taks. However the way it is implemented in this RFC is not something I would like to work with for a decade or so. The performance gain is also not sufficient enough to justify it. I think we should think more about other options (no matter how long you spent discussing options before posting this RFC). I am sure we can come with other solutions which may be cleaner and also provide some performance improvements. > If we break APIs anyways: Can't we go for C++ which allows providing > high level APIs with high performance ... Yes, C++ would in this case provides almost all we need for implementing parameter management in a clean and efficient way. Not sure if it is desired tho'. By the way, please do not ask me to come with code and cases to valid my comment here, I won't. At least not until things get clarified about we wish. The last thing we need is yet another Zend vs World about that :) Cheers, --=20 Pierre @pierrejoye | http://www.libgd.org