Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71065
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.215.176 as permitted sender)
Content-Type: multipart/alternative; boundary="Apple-Mail=_C49ECDC6-66BF-4CCA-BC7E-59BEF4EC9421"
Message-ID: <581A185E-0F00-4B49-AA87-859D75E63BA2@googlemail.com>
Date: Sat, 11 Jan 2014 16:42:45 +0100
To: PHP internals <internals@lists.php.net>
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Subject: Revisiting the "Named Arguments" RFC
From: ingwie2000@googlemail.com (Kevin Ingwersen)

--Apple-Mail=_C49ECDC6-66BF-4CCA-BC7E-59BEF4EC9421
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

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 =
opinion, that=92d be a very useful addition - as many modern languages =
support this 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 =
really see anything of its current state on the page itself.

Kind regards,
Ingwie=

--Apple-Mail=_C49ECDC6-66BF-4CCA-BC7E-59BEF4EC9421--