Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68935 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87932 invoked from network); 7 Sep 2013 05:56:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Sep 2013 05:56:28 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:53312] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3C/D2-00660-A00CA225 for ; Sat, 07 Sep 2013 01:56:27 -0400 Received: (qmail 26865 invoked by uid 89); 7 Sep 2013 05:56:23 -0000 Received: from unknown (HELO linux-dev4.lsces.org.uk) (lester@rainbowdigitalmedia.org.uk@86.178.188.140) by mail4.serversure.net with ESMTPA; 7 Sep 2013 05:56:23 -0000 Message-ID: <522AC0F2.2050608@lsces.co.uk> Date: Sat, 07 Sep 2013 07:00:18 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20 MIME-Version: 1.0 To: "internals@lists.php.net >> PHP internals" References: <522A87EB.7080702@rotorised.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Named parameters From: lester@lsces.co.uk (Lester Caine) Matthew Leverton wrote: > On Fri, Sep 6, 2013 at 8:56 PM, Ryan McCue wrote: >> Matthew Leverton wrote: >> This is already the case. In libraries that accept options via an array, >> those array keys are pretty much set in stone (although you can map them >> if you need to change a key). >> > The big difference here is if I accept an options array, I understand > that the keys are important and would never break backward > compatibility by changing a parameter name. This isn't a case of "if > you don't like it, then don't use it" because every function I create > now has to respect the possibility of accepting named parameters, > whether I care about it or not. And I sure hope every function I call > is created by and maintained by somebody with those same > sensibilities. > > My opinion is that this really isn't as cool as it sounds, especially > since we have short array syntax. Again, I don't really care if it's > accepted into PHP, but I think it will be more of a minor nuisance for > me than anything else. I'll second that statement. It will be more reason for me to stop following PHP 'upgrades' in the future. I'm already holding off 5.5 as it gives me nothing that I want. This would be a reason to make that permanent. I would add that one of the reasons I moved TO PHP was the fact that it did not have the overhead of named parameters, amongst other things which have also been lost over the last few years. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk