Re: Re: Named arguments revisited
| From: | jared at intuitivefuture dot com | Date: | Fri, 13 Jan 2006 22:45:08 +0000 |
| Subject: | Re: Re: Named arguments revisited | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-21524@lists.php.net to get a copy of this message | ||
This isn't a waste of bandwidth. This is about the future of the language
and about the fact that PHP is missing a crucial feature that several
other languages have had for years and others are working on -- PHP's
competition, in other words.
Please explain to me how using an array is a solution. As I see it, it's
not. It's a hack. It gives you nothing...no code-completion, no error
checking, no built-in documentation -- not even type hinting which was a
nice add-on for PHP 5.
I don't mean to sound antagonistic, but there's only one justification I
can see for not implementing named parameters and that's time. Actually
defending a design decision of rejecting it quite frankly astonishes me.
Jared
> Guys,
>
> It's not going to happen. Please move on. We've discussed it lots of
> times in the past. Many times we've come to the conclusion that for a
> few cases it's not worth it.
> If you have functions with lots of parameters (probably 3-4 in a
> whole application) then just use array()'s. It's actually not a
> mediocre but a pretty decent solution.
>
> Don't mean to be abrupt but we waste so much bandwidth here on things
> we've already discussed in the past, and most of the main dev's
> clearly aren't in favor.
>
> Andi