Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95016 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37915 invoked from network); 10 Aug 2016 17:23:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Aug 2016 17:23:20 -0000 X-Host-Fingerprint: 90.217.82.232 unknown Received: from [90.217.82.232] ([90.217.82.232:1294] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 47/D0-32735-7036BA75 for ; Wed, 10 Aug 2016 13:23:20 -0400 Message-ID: <47.D0.32735.7036BA75@pb1.pair.com> To: internals@lists.php.net References: Date: Wed, 10 Aug 2016 18:23:15 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 90.217.82.232 Subject: Re: [PHP-DEV] Re: The death of `#ifndef FAST_ZPP`? From: ajf@ajf.me (Andrea Faulds) Hi Yasuo, Yasuo Ohgaki wrote: > I've asked the same question before I start eliminating old style parse API. > > Dimitry said it's designed to optimize heavily called functions, not > for ease of use and the RFC for fast zpp states "keep old parameter > parsing API", so I don't have to bother. Oh, yeah, I've heard about that. Even if it wasn't specifically intended to be a friendlier API, though, I've heard at least one other person say they prefer using FAST_ZPP, and I prefer it myself. It's more verbose, but it's easier to read at-a-glance, and it makes mistakes more obvious. Thanks. -- Andrea Faulds https://ajf.me/