Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80481
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.177 as permitted sender)
MIME-Version: 1.0
Reply-To: marcio3w@gmail.com
In-Reply-To: <54B6C047.3070301@mabe.berlin>
References: <52243BA6.5040905@sugarcrm.com> <54B6C047.3070301@mabe.berlin>
Date: Wed, 14 Jan 2015 16:33:22 -0300
Message-ID: <CAOsHV+ua87pdP+bmy18+ds6roBaiGnoRD7iid=q7ZXPhQzWYHQ@mail.gmail.com>
To: Marc Bennewitz <dev@mabe.berlin>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1134730e3cc10f050ca1d12d
Subject: Re: [PHP-DEV] [RFC] Skipping parameters take 2
From: marcio.web2@gmail.com (Marcio Almada)

--001a1134730e3cc10f050ca1d12d
Content-Type: text/plain; charset=UTF-8

Marc Bennewitz, Stas,

> But I think adding "default" as new keyword is a big BC break!
> I personally also don't like it and asked myself why can't the parameter
simply skipped?

Default is already a reserved word AFAIK. But I've been thinking about
alternatives to parameter skipping syntax which brought  me the Golang
blank identifier _ to mind:

    create_query("deleted=0", "name", _, _, true);

Still not sure if it's better than `default`, though.

2015-01-14 16:15 GMT-03:00 Marc Bennewitz <dev@mabe.berlin>:

> Hi Stas,
>
> I really like this RFC. It makes it simple to use defined defaults without
> the need to know about them of to updated.
>
> But I think adding "default" as new keyword is a big BC break!
> I personally also don't like it and asked myself why can't the parameter
> simply skipped?
>
>     function foo ($a='a', $b='b') {}
>
>     foo();
>     foo($a);
>     foo(, $b);
>     foo($a,);
>     foo(,);
>
> Is it possible to use the default parameter on inheritance?
>
> class Bar {
>     function foo($a='a', $b='b') {}
> }
>
> class Baz extends Bar {
>     function foo($a=default, $b=default) {
>         // do something
>         parent::foo($a, $b);
>     }
> }
>
>
> Marc
>
>
> Am 02.09.2013 um 09:17 schrieb Stas Malyshev:
>
>> 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 :)
>>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a1134730e3cc10f050ca1d12d--