Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47820
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.211.200 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=yIWcMhORtifaX2Lgr2vzg4iXUUMLZpJvABrwZGi21KYyfrOubuzZgJbPWfa8Ari7BQ
         DU3zpFxSJJgjEQJ4QZRUX/uTl31RyLnO5i3NZz0XUzKucJnoPHLYHNifESY+/5pcukkd
         6izpner50D5FFfYr0WguEHnOMhHHcNTo973RE=
MIME-Version: 1.0
Sender: tjerk.meesters@gmail.com
In-Reply-To: <4BBC25DD.7060604@divbyzero.net>
References: <745C5243-EB51-4D43-B036-8A34CDBBB547@gregory.net>
	 <4BB68D61.2070301@lerdorf.com> <4BB6938F.7090404@zend.com>
	 <u2l7f3ed2c31004031900o5ea084f7m257c3bcb0e7716cc@mail.gmail.com>
	 <4BB90DB7.6060706@zend.com>
	 <s2vfe05d1541004041545k19b4b132yba1875d45b6e19ac@mail.gmail.com>
	 <4BBC25DD.7060604@divbyzero.net>
Date: Wed, 7 Apr 2010 20:35:36 +0800
Message-ID: <t2nb9defe2f1004070535k97ea2c9z8274058cc05af45b@mail.gmail.com>
To: Martin Jansen <martin@divbyzero.net>, Pierre Joye <pierre.php@gmail.com>, 
	Stanislav Malyshev <stas@zend.com>, Hannes Magnusson <hannes.magnusson@gmail.com>, GM <gregory@gregory.net>, 
	internals@lists.php.net, Rasmus Lerdorf <rasmus@lerdorf.com>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Named Parameters
From: datibbaw@php.net (Tjerk Anne Meesters)

In the case whereby names parameters are "plucked" from the argument
list and passed as a hash to the function it really shouldn't matter
whether that's invalid in python; both (2, 'name' => 'test') and
('name' => 'test', 2) would yield the same results, albeit it's a
highly dubious way of passing arguments ;-)

On 4/7/10, Martin Jansen <martin@divbyzero.net> wrote:
> On 5.4.2010 00:45, Pierre Joye wrote:
>> On Mon, Apr 5, 2010 at 12:07 AM, Stanislav Malyshev <stas@zend.com> wrote:
>>
>>> 3. Combining named and un-named params can get weird - i.e. foo(1,2,3) is
>>> simple, foo(1, 2, bar => 3) is doable, but foo(1, 2, bar => 3, 4) would
>>> be
>>> trouble, since it is not clear at all where 4 should go to. Moreover,
>>
>> If we introduce named argument, mixing them should not be weird. An
>> argument can have both a name and a position, allowing combination of
>> normal or named arguments. Python's way to do it is very nice and
>> handy:
>>
>> http://diveintopython.org/power_of_introspection/optional_arguments.html
>
> Just to be clear about this:  Python does not allow using an unnamed
> parameter after a named parameter occurred, i.e. foo(bar = 3, 2) is not
> valid there.
>
> I would go as far as disallowing mixing of named and unnamed parameters
> completely.  But that's probably just me.
>
> - Martin
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
--
Tjerk