Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68760
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <893f9c06c8fe43188f9e4d09fc0594b7@BN1PR07MB135.namprd07.prod.outlook.com>
References: <CAF+90c8oxd4j4sj6AL+TdYu6_AoroWk1=RPdKrE7PNBs2XZg=A@mail.gmail.com>
 <893f9c06c8fe43188f9e4d09fc0594b7@BN1PR07MB135.namprd07.prod.outlook.com>
Date: Fri, 30 Aug 2013 23:34:43 +0200
Message-ID: <CALtuQzAFENyoK=0MgWjjU_32Hq+ji7JjhKuSF1rDcxO0TEJ7Qw@mail.gmail.com>
To: "jbondc@openmv.com" <jbondc@openmv.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=e89a8f3baedf04f61404e5310054
Subject: Re: [PHP-DEV] [RFC] Syntax for variadic functions
From: krebs.seb@gmail.com (Sebastian Krebs)

--e89a8f3baedf04f61404e5310054
Content-Type: text/plain; charset=ISO-8859-1

2013/8/30 jbondc@openmv.com <jbondc@openmv.com>

> On Wed Aug 28 11:47 AM, Nikita Popov wrote:
> >
> >     https://wiki.php.net/rfc/variadics
>
> Interesting idea, expanding on:
>
> function log($message, ...$options) {}
>
> It would seem convenient to allow ...$options to be passed as a key-value
> array of arguments as well:
> function logA($message, ...$options[]) {  echo count($options); }
>
> logA("foo"); // 0
> logA("foo", 1, 2); // 2
> logA("foo", array(1,2,3)); // 3
>
> The difference here is that variadic options is declared as an optional
> array, it would not support a 'typehint' forcing all arguments to be of the
> same type.
> It could be a way to support ~ named parameters
>
> // requires at least 1 argument named as 'level'
> function logB($message, ...$options['level']) {
>    echo $options['level'] .' '. count($options);
> }
>
> logB("foo");                                    // fails: 'level' argument
> missing
> logB("foo", 'notice');                   //notice 1
> logB("foo", ['level' => 'notice']); // notice 1
> logB("foo", 'notice', 'extra'); // notice 2
> logB("foo", ['level' => 'notice'], 'extra'); // notice 2
>
> // requires min 2 arguments
> function logC($message, ...$options['level','priority']) {
>    echo 'level:'. $options['level'];
>    echo 'priority:'. $options['priority'];
> }
> logC("foo", "notice", 4);
> logC("foo", ['level' => 'notice', 'priority' => 4]);
>
> That would remove the need for a "splat" or "scatter" operator. The
> declaration "...$options[]" would mean, I accept an array of arguments
> followed by extra arguments
>

I'd recommend to use an object, or separate parameters instead. Thats not a
use-case for argument-lists.


Regards
Sebastian


>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
github.com/KingCrunch

--e89a8f3baedf04f61404e5310054--