Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71077
Return-Path: <dygear@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 64175 invoked from network); 12 Jan 2014 07:09:37 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 12 Jan 2014 07:09:37 -0000
Authentication-Results: pb1.pair.com header.from=dygear@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=dygear@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.173 as permitted sender)
X-PHP-List-Original-Sender: dygear@gmail.com
X-Host-Fingerprint: 209.85.216.173 mail-qc0-f173.google.com  
Received: from [209.85.216.173] ([209.85.216.173:39668] helo=mail-qc0-f173.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id AA/F3-36150-0BF32D25 for <internals@lists.php.net>; Sun, 12 Jan 2014 02:09:36 -0500
Received: by mail-qc0-f173.google.com with SMTP id i8so1911719qcq.18
        for <internals@lists.php.net>; Sat, 11 Jan 2014 23:09:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date:cc
         :content-transfer-encoding:message-id:references:to;
        bh=m6fq2u+L/uf7zTBoNjntO00O1Fq6fvGwnEEdTkUbgn8=;
        b=swsY8aCGyjv2htG6Pgh+NJH7wLt0+RzjAT7SZ8nuZlEp1it8msNg9cdusz+D8NcQGS
         Pr1d8TzWHzxmamzkIVXBbhIR38QzV7sdDcrjOPYlpaCmbDiQw1HEKDt+bqtpnIcCVahT
         Lpd4jFHPmJU2roOc3MRROmz+M1yUfRICoQUmM9ekZ/JzGMny2edpZ7aeb8Oeg42jmjV7
         7PkqUuhG8aPlrauDDxPZ+xVzW7Dx1ds9Cf6LDVHDPre9vzeaom9l8fHUv4euDA+wIHE8
         ofgn9KCrrQsrEvZrlD/bR7TyZ5oaz3eRdINoCox1ZyskbRm3VsGJqY2um7drjCPtBexo
         r9dw==
X-Received: by 10.224.113.204 with SMTP id b12mr25325200qaq.35.1389510573745;
        Sat, 11 Jan 2014 23:09:33 -0800 (PST)
Received: from [192.168.1.6] (ool-4352ee3d.dyn.optonline.net. [67.82.238.61])
        by mx.google.com with ESMTPSA id hb2sm22149583qeb.6.2014.01.11.23.09.31
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Sat, 11 Jan 2014 23:09:31 -0800 (PST)
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
X-Mailer: iPad Mail (11B554a)
In-Reply-To: <CABDNdAEOF6TeEiWRM6WfxNk6ex7SGPheTSzxX+59ryDg+ErV6Q@mail.gmail.com>
Date: Sun, 12 Jan 2014 02:09:31 -0500
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <CF9D21D9-2D55-4DB6-9224-4D53EEBB206E@gmail.com>
References: <581A185E-0F00-4B49-AA87-859D75E63BA2@googlemail.com> <CABDNdAEOF6TeEiWRM6WfxNk6ex7SGPheTSzxX+59ryDg+ErV6Q@mail.gmail.com>
To: Philip Sturgeon <pjsturgeon@gmail.com>
Subject: Re: [PHP-DEV] Revisiting the "Named Arguments" RFC
From: dygear@gmail.com (Mark Tomlin)

Just as a guy in the outside looking in, it would be great to have this. I r=
eally hope to see it in 5.6.

Thank You For Your Time,
Mark 'Dygear' Tomlin

> On Jan 11, 2014, at 10:50 AM, Philip Sturgeon <pjsturgeon@gmail.com> wrote=
:
>=20
> I've heard that it's waiting for the EngineException RFC to go
> through, as the implementation with it is much stronger than without
> it.
>=20
> On Sat, Jan 11, 2014 at 10:42 AM, Kevin Ingwersen
> <ingwie2000@googlemail.com> wrote:
>> Hello there.
>>=20
>> Within one of the recent votes, I was reminded upon an RFC for named para=
meters/arguments - to be exact, this one: https://wiki.php.net/rfc/named_par=
ams
>>=20
>> I just wanted to know if this RFC is still in discussion, has been droppe=
d, or what else is currently being up with it. Because in my opinion, that=E2=
=80=99d be a very useful addition - as many modern languages support this ki=
nd of feature already. The only language that I personaly am using that supp=
orts that is Objective-C - and in there, it is very useful. Although its qui=
te different - it=E2=80=99s a different call-style entirely - I could imagin=
e the implementation from the link above to be very useful in PHP.
>>=20
>> It would be great to know the current state of the RFC, as I didn=E2=80=99=
t really see anything of its current state on the page itself.
>>=20
>> Kind regards,
>> Ingwie
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20