Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68932 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76475 invoked from network); 7 Sep 2013 01:57:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Sep 2013 01:57:01 -0000 Authentication-Results: pb1.pair.com header.from=lists@rotorised.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lists@rotorised.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rotorised.com from 203.88.126.58 cause and error) X-PHP-List-Original-Sender: lists@rotorised.com X-Host-Fingerprint: 203.88.126.58 mta58-d1.ip2.cbr1.mail-filtering.com.au Received: from [203.88.126.58] ([203.88.126.58:64798] helo=mta58-d1.ip2.cbr1.mail-filtering.com.au) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A9/11-00660-9E78A225 for ; Fri, 06 Sep 2013 21:56:59 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgABAE6HKlKva64TfGdsb2JhbABbgzzCN4EoFg4BAQkYBT6CJAEBBXgRCw0LCRYPCQMCAQIBRRMIAQGHfcE6kAMWhAcDmSSEaTuORQ X-IPAS-Result: AgABAE6HKlKva64TfGdsb2JhbABbgzzCN4EoFg4BAQkYBT6CJAEBBXgRCw0LCRYPCQMCAQIBRRMIAQGHfcE6kAMWhAcDmSSEaTuORQ X-IronPort-AV: E=Sophos;i="4.90,858,1371045600"; d="scan'208";a="218869085" Received: from unknown (HELO ub005lcs09.cbr.the-server.net.au) ([175.107.174.19]) by smtp-data2.ironport2.cbr1.mail-filtering.com.au with ESMTP; 07 Sep 2013 11:56:55 +1000 Received: from 217.33.96.58.static.exetel.com.au ([58.96.33.217]:50410 helo=[192.168.1.134]) by ub005lcs09.cbr.the-server.net.au with esmtpa (Exim 4.80.1) (envelope-from ) id 1VI7lb-003a2j-7g for internals@lists.php.net; Sat, 07 Sep 2013 11:56:51 +1000 Message-ID: <522A87EB.7080702@rotorised.com> Date: Sat, 07 Sep 2013 11:56:59 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Named parameters From: lists@rotorised.com (Ryan McCue) Matthew Leverton wrote: > What I don't like about named parameters is that if I build a library, > now even my parameter names are unchangeable if I don't want to break > any backward compatibility, since I never know if somebody will decide > to call my single parameter method with named parameters. Are we > prepared to go through every PHP function and make sure the names of > the parameters are set in stone before this feature would go live? 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). All this does is add first-class support in the language. Huge +1 for this feature and thank you to Nikita for working on the RFC. -- Ryan McCue