Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68918
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CADajX4Dv2eC_d-BQCqHyY8G6AiPyHuG1TcDPcdgSYAz0DYnMJA@mail.gmail.com>
References: <CAF+90c85v_VTPTPanBcTJ70Ff6pm6fRgAGs4n1uoaA+B9UZg=w@mail.gmail.com>
 <CADajX4Dv2eC_d-BQCqHyY8G6AiPyHuG1TcDPcdgSYAz0DYnMJA@mail.gmail.com>
Date: Fri, 6 Sep 2013 19:55:19 +0200
Message-ID: <CAMyk_AYpfdZMCMtZtkLJbJ1aOGikR_YU+tMT5czQr8VOwk=hEQ@mail.gmail.com>
To: Adam Harvey <aharvey@php.net>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01227b7c1fe11a04e5babfc9
Subject: Re: [PHP-DEV] [RFC] Named parameters
From: linepogl@gmail.com (Lazare Inepologlou)

--089e01227b7c1fe11a04e5babfc9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2013/9/6 Adam Harvey <aharvey@php.net>
>
>
> Variadics/splat: collecting both named and positional arguments into
> one array seems reasonable to me. I think the main use case there
> would be option parameters, which you'd have to validate anyway, so
> positional parameters would be dealt with at that point =E2=80=94 I don't=
 see
> separate arrays as conferring any great advantage in terms of
> validating parameters, and it's no simpler conceptually.
>
>
There is a small drawback. Suppose this code:

function foo( $bar =3D 0 , ...$args ){}
foo( bart =3D> 3 ); // misspelled name

According to the RFC, any unknown argument name will fall into the $args
array, making the above code valid. As this cannot be verified statically,
it is a possible source of bugs.




Lazare INEPOLOGLOU
Ing=C3=A9nieur Logiciel

--089e01227b7c1fe11a04e5babfc9--