Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:27799
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain cschneid.com from 195.226.6.51 cause and error)
Message-ID: <45C70AA2.2070603@cschneid.com>
Date: Mon, 05 Feb 2007 11:44:50 +0100
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: Lukas Kahwe Smith <mls@pooteeweet.org>
CC:  internals@lists.php.net
References: <011701c7482d$a39f6910$6500a8c0@zend.2k>    <45C5EC63.7030605@cschneid.com> <1902.67.184.122.32.1170651145.squirrel@www.l-i-e.com> <45C704F0.4040703@cschneid.com> <45C706CF.8090908@pooteeweet.org>
In-Reply-To: <45C706CF.8090908@pooteeweet.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Named parameters, was Syntactic improvement to array]
From: cschneid@cschneid.com (Christian Schneider)

Lukas Kahwe Smith wrote:
> Named parameters is not just syntax sugar, as they would make it 
> possible to get compiler errors and phpoc support automatically over 
> having to implement some array based solution to trigger errors and some 

Not 'our' way of named parameters where the main feature is the var-args 
like behaviour of the parameter list, i.e. being able to pass in 
"unknown" parameters. Useful for e.g. HTML generation or DB queries 
where you can then map parameter names to HTML attributes or DB fields 
respectively. So they are effectively an associative array and syntactic 
sugar was good enough for us.

But that's a completely different direction than the and more more 
strict way PHP is heading (PPP, typehints, ...) so The List(tm) won't 
like ;-)

- Chris