Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85529
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.215.49 cause and error)
MIME-Version: 1.0
In-Reply-To: <76D3DA4F-06EE-4F6B-893E-1D111FAD3C2C@gm.lv>
References: <76D3DA4F-06EE-4F6B-893E-1D111FAD3C2C@gm.lv>
Date: Sun, 29 Mar 2015 14:56:33 +0000
Message-ID: <CA+kxMuQdnc-u0Gk1+t_e0RtgcFbBLFgDVdnTiwmeSq2H-Zbc1w@mail.gmail.com>
To: Gints Murans <gm@gm.lv>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Named parameters
From: danack@basereality.com (Dan Ackroyd)

On 29 March 2015 at 12:28, Gints Murans <gm@gm.lv> wrote:

> What happened to this RFC? This is a really great idea for php.

The 'Skip Params' RFC (https://wiki.php.net/rfc/skipparams) went to
vote and was declined.
The 'named params' RFC (https://wiki.php.net/rfc/named_params) author
has been working on stuff they feel is more important.

> Reading over some old code, this way it would be a lot easier to understand what that second parameter boolean = true is:

You can do this right now, if you want to:

getIdByTitle('sample', $insert = true);

> About syntax: $insert => true seems kind of confusing:
>        $insert = true;
>       getIdByTitle('sample', $insert => $insert)

You shouldn't need it for the case where you're actually already using
a parameter e.g. `getIdByTitle('sample', $insert);` already indicates
what the parameter is. The only place where you could argue this
syntax is needed is when you're passing in just a bare 'true' which
has no syntactic meaning associated with it.

That syntax works for all versions of PHP, so I guess a new syntax
that achieves the same thing is unlikely to be that popular an idea.

cheers
Dan