Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47848
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <t2g10845a341004060316q1dd2ccaasdb3c9d2fd933e39f@mail.gmail.com>
Date: Fri, 9 Apr 2010 22:41:29 +0200
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <981BD9EA-F604-4FB9-9D28-CBE7EC027566@pooteeweet.org>
References: <t2g10845a341004060316q1dd2ccaasdb3c9d2fd933e39f@mail.gmail.com>
To: RQuadling@googlemail.com
Subject: Re: [PHP-DEV] Supplying nothing at all for default parameters
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 06.04.2010, at 12:16, Richard Quadling wrote:

> Hello.
>=20
> A suggestion I would like to make is to allow for nothing to be
> supplied for defaulted parameters.
>=20
> I suppose the easiest way of describing this issue is with the
> following code ...
>=20
> <?php
> function foo($bar, $baz =3D 9, $buzz =3D 10) {
> return "$bar $baz $buzz";
> }
>=20
> // Whatever is supplied for $baz will be used for $baz.
> // User has to know the default value of $baz rather than just
> allowing the default value.
> echo foo(1, 9, 20);
>=20
> I don't know the stylics on using default parameters, but for the user
> to have to know the default value would sort of make the default
> redundant.
>=20
>=20
> // Passing nothing at all could be one option.
> echo foo(1, , 20);


i dont think is really a nice syntax to support. either we add named =
parameters are you just use the current work around for the absence of =
named parameters (aka an array parameter and =
array_merge/array_replace_recursive)

regards,
Lukas Kahwe Smith
mls@pooteeweet.org