Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71082
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <581A185E-0F00-4B49-AA87-859D75E63BA2@googlemail.com>
References: <581A185E-0F00-4B49-AA87-859D75E63BA2@googlemail.com>
Date: Sun, 12 Jan 2014 11:27:22 +0100
Message-ID: <CAF+90c8L7WP8Hch=DSWKD6Hb_=1=aKMzj49-1_eTbCgjwDNPWA@mail.gmail.com>
To: Kevin Ingwersen <ingwie2000@googlemail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c1d6a89f46dd04efc3674f
Subject: Re: [PHP-DEV] Revisiting the "Named Arguments" RFC
From: nikita.ppv@gmail.com (Nikita Popov)

--001a11c1d6a89f46dd04efc3674f
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Sat, Jan 11, 2014 at 4:42 PM, Kevin Ingwersen
<ingwie2000@googlemail.com>wrote:

> Hello there.
>
> Within one of the recent votes, I was reminded upon an RFC for named
> parameters/arguments - to be exact, this one:
> https://wiki.php.net/rfc/named_params
>
> I just wanted to know if this RFC is still in discussion, has been
> dropped, or what else is currently being up with it. Because in my opinio=
n,
> that=92d be a very useful addition - as many modern languages support thi=
s
> kind of feature already. The only language that I personaly am using that
> supports that is Objective-C - and in there, it is very useful. Although
> its quite different - it=92s a different call-style entirely - I could
> imagine the implementation from the link above to be very useful in PHP.
>
> It would be great to know the current state of the RFC, as I didn=92t rea=
lly
> see anything of its current state on the page itself.
>

A quick summary:

The open questions are mostly resolved, namely: Variadics / unpacking on
named args should use same syntax as for not-named args. No signature
checks should be introduced, instead use runtime errors. The question of
syntax wasn't yet entirely clear, though that's something one could just
vote, if need be.

The patch itself is also finished from the "general feature implementation"
side. What is missing are updates to internal functions. Namely all arginfo
structs should be made consistent across functions and synced with the
docs. Also we need to ensure that argument parsing for internal functions
works correctly everywhere.

Feature freeze for 5.6 is in two months and the last two points require a
huge amount of work (because of the sheer number of functions in our
standard library). I started a bit on the arginfo part, by updating the
parameter names for array functions in the docs, but didn't continue that
effort as other things got in the way. I don't think I'll have enough time
to finish this before 5.6 FF.

So, likely this will be postponed to the next version of PHP ;)

Nikita

--001a11c1d6a89f46dd04efc3674f--