Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20912 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54792 invoked by uid 1010); 30 Nov 2005 21:51:29 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 54776 invoked from network); 30 Nov 2005 21:51:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Nov 2005 21:51:29 -0000 X-Host-Fingerprint: 216.145.54.171 mrout1.yahoo.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from ([216.145.54.171:47264] helo=mrout1.yahoo.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id E2/32-14828-0EE1E834 for ; Wed, 30 Nov 2005 16:51:29 -0500 Received: from [66.228.175.145] (borndress-lm.corp.yahoo.com [66.228.175.145]) by mrout1.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id jAULnmrg088940; Wed, 30 Nov 2005 13:49:48 -0800 (PST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID: <374c2968dd7f3d13c696037ef850256f@gravitonic.com> Content-Transfer-Encoding: 7bit Cc: internals@lists.php.net Date: Wed, 30 Nov 2005 13:50:23 -0800 To: Jared White X-Mailer: Apple Mail (2.623) Subject: Re: [PHP-DEV] Named arguments revisited From: andrei@gravitonic.com (Andrei Zmievski) Can you explain your reasoning behind "essential for using PHP as a solid templating language" and "nothing is a good substitute for the real deal"? - Andrei On Nov 29, 2005, at 11:17 PM, Jared White wrote: > Named arguments are absolutely essential for using PHP as a solid > templating language, and, in fact, they also greatly enhance code > readability for complex method calls of in-depth APIs. My experience > with both Objective-C and Python has showed me the wonders and joys of > named arguments, and it is something I've desperately wanted in PHP > for ages. I'm sure I'm not alone in this. I've tried array constructs, > multiple arguments with string-based names and fancy parsing using > func_get_args(), and various combinations thereof, and nothing is a > good substitute for the real deal.