Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10735
Return-Path: <schlueter@phpbar.de>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 51020 invoked by uid 1010); 23 Jun 2004 19:41:47 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 50975 invoked by uid 1007); 23 Jun 2004 19:41:47 -0000
Message-ID: <20040623194144.50832.qmail@pb1.pair.com>
To: internals@lists.php.net, Daniel Crookston <daniel@hyperion-data.net>
Date: Wed, 23 Jun 2004 21:41:39 +0200
References: <20040623150429.E62456@hyperion-data.net> <40D9A954.1040403@cschneid.com> <20040623193350.D22728@hyperion-data.net>
Lines: 32
User-Agent: KNode/0.7.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Posted-By: 84.128.46.163
Subject: Re: keyword arguments?
From: schlueter@phpbar.de (Johannes Schlueter)

Hi Daniel,

named paramters should only be followed by named paramters - like with
default values. So one can first "fill" the unnamed once and then some (or
all) of the named once.

But remembering the last discussion on this idea I don't think this will be
added...

johannes

Daniel Crookston wrote:

> Actually, that would be acceptable, since you lose the bulk of array().
> The only thing that remains a problem is that if you add another
> (non-named) parameter, you still need to worry about the relative
> positions in all of your functions.  Now that I think about it, that's
> actually a bigger complaint for me than having to use array().
> 
> Thoughts?  Comments?  Flames?
> 
> Daniel
> 
> P.S. Thank you for the link to the patches :)
> 
>> ---------------------------------------------------------------------
>>
>> I'm still in favor of an approach we are using here where you can pass
>> associative arrays without array():
> 
> <snip all else>