Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68933 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80565 invoked from network); 7 Sep 2013 03:29:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Sep 2013 03:29:13 -0000 Authentication-Results: pb1.pair.com header.from=leverton@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=leverton@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.180 as permitted sender) X-PHP-List-Original-Sender: leverton@gmail.com X-Host-Fingerprint: 209.85.214.180 mail-ob0-f180.google.com Received: from [209.85.214.180] ([209.85.214.180:41341] helo=mail-ob0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5C/B1-00660-78D9A225 for ; Fri, 06 Sep 2013 23:29:11 -0400 Received: by mail-ob0-f180.google.com with SMTP id v19so4263449obq.11 for ; Fri, 06 Sep 2013 20:29:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=D2tjpOWYrD4U/mT5SvRbL8jg8vK1Cqse007puMxNIZE=; b=A2cV4/G5Ds3mV6YQn37+1IsfjWdSGw/96TR0FXERUvF+ZGDFdUQekJB+btmrU8CQl5 0U4ewVOjLXnEy+hpaKxDHNRBuRh5Hs7eIbdoObTr+ZddfzDaXHYtNp1x+jS1h3hL6xKd VXOtQyFK0g0uVsazVS1dSu1uC2J0CypzfyjVPRMbR+evF47e5qsNtZawYo2f9y0ziKA7 2rQVbVvWKHAq4CeNX+eAz2Qkfr+ZrSFa1iBbZrAhWRxV3ucCf0RjidVWDF7jZWMXNW4f LYhDbCax1VV7t+DcCpbpRCV6z1WftIemVKHgAQE8czEAjywf+m0y8iqJKq1zn4qkSogr s4Dg== MIME-Version: 1.0 X-Received: by 10.182.120.132 with SMTP id lc4mr4239344obb.7.1378524548831; Fri, 06 Sep 2013 20:29:08 -0700 (PDT) Received: by 10.182.133.34 with HTTP; Fri, 6 Sep 2013 20:29:08 -0700 (PDT) In-Reply-To: <522A87EB.7080702@rotorised.com> References: <522A87EB.7080702@rotorised.com> Date: Fri, 6 Sep 2013 22:29:08 -0500 Message-ID: To: Ryan McCue Cc: PHP internals Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] [RFC] Named parameters From: leverton@gmail.com (Matthew Leverton) 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. -- Matthew Leverton