Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68910
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
In-Reply-To: <CAF+90c85v_VTPTPanBcTJ70Ff6pm6fRgAGs4n1uoaA+B9UZg=w@mail.gmail.com>
References: <CAF+90c85v_VTPTPanBcTJ70Ff6pm6fRgAGs4n1uoaA+B9UZg=w@mail.gmail.com>
Date: Fri, 6 Sep 2013 17:59:41 +0100
Message-ID: <CAD6=DWfy7BRSF-gG+Est97hPR9aGcDZ=w0oeQVGaXvwUb39ELg@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [RFC] Named parameters
From: garoevans@gmail.com (Gareth Evans)

I like!

My preference on syntax is;

test(:foo => "oof", :bar => "rab");

I don't think;

test("foo" => "oof", "bar" => "rab");

denotes enough emphasis on any part in-particular, and the downsides
of other implementations are mentioned, such as variable names and
collisions with reserved keywords.

Thanks,
Gareth

On 6 September 2013 17:39, Nikita Popov <nikita.ppv@gmail.com> wrote:
> Hi internals!
>
> I created an RFC and preliminary implementation for named parameters:
>
>     https://wiki.php.net/rfc/named_params
>
> The RFC and implementation are not yet complete. I mainly want to have
> feedback on the idea in general and on the Open Questions (
> https://wiki.php.net/rfc/named_params#open_questions) in particular.
>
> Thanks,
> Nikita