Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68847
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <52243BA6.5040905@sugarcrm.com>
References: <52243BA6.5040905@sugarcrm.com>
Date: Mon, 2 Sep 2013 14:32:16 +0200
Message-ID: <CAEZPtU5u+29CxpgDHs6GOoDUU+EWtm-8dr7NL4dufvSq+LZsyw@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [RFC] Skipping parameters take 2
From: pierre.php@gmail.com (Pierre Joye)

hi Stas,

On Mon, Sep 2, 2013 at 9:17 AM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
> I've finally took some time to revive the skipping parameter RFC and
> patch. For those who doesn't remember what it is please see:
> https://wiki.php.net/rfc/skipparams
> TLDR version:
>
> The idea is to allow skipping parameters in function with optional
> arguments so that this:
>    function create_query($where, $order_by, $join_type='INNER', $execute
> = false, $report_errors = true)
>
> can be called like this:
>     create_query("deleted=0", "name", default, default,
> /*report_errors*/ true);
>
> Instead of trying to remember what the defaults are.
> The patch is here:
>
> https://github.com/php/php-src/pull/426
>
> Any comments or feedback on the RFCs and the code are welcome,
> especially pointing out the cases where it may not work (which means we
> need more phpt's there :)

Using default instead of ,,, is indeed much more readable.

However I still wonder what prevents to finally implement named
parameters too, it will provide the same feature while being even more
handy and easier. I could dig the archives but I don't remember what
was the reason why we rejected the idea back then.

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org