Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60679
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CA+aNemYeQmWXGXCa7hosh2WyBq7zWh9bmgFLrOd5V=v=-cBQsg@mail.gmail.com>
References: <CA+aNemYeQmWXGXCa7hosh2WyBq7zWh9bmgFLrOd5V=v=-cBQsg@mail.gmail.com>
Date: Sun, 27 May 2012 19:03:28 +0100
Message-ID: <CA+yzxZh7aDoj8CiS82KNARf8KfLxDNhGx2Hix-H6PwXjK1d-+A@mail.gmail.com>
To: Mathias Grimm <mathiasgrimm@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=20cf303ea76892a38404c1086d31
Subject: Re: [PHP-DEV] RFC Skipping optional parameters for functions
From: admacedo@gmail.com (Daniel Macedo)

--20cf303ea76892a38404c1086d31
Content-Type: text/plain; charset=ISO-8859-1

NOTE: Although related/solving some of the same problems; skipping optional
parameters (several commas or using 'default' keyword) is different from
using named parameters.
And both have different supporters/haters over each change.

I wouldn't like to restart the whole debate over the KISS, "Not the PHP
way", or the alternate ways work around the original issue.

But on a personal opinion, I'd like to see named parameters implemented -
which also solves the skipping optionals regardless of the order - the only
concern of the community at large might be the proper syntax..

I also suggested the even shorter array syntax for 5.4:
http://php.net/migration54.new-features
Which would use the colon as a separator
$a = ['one': 1, 'two': 2, 'three': 3, 'four': 4];

And the idea it would be simpler/efficient/readable inspired some dissent
over both the readability and the PHP-way.

So I'm not sure if your suggestion won't keep the same issue...

--20cf303ea76892a38404c1086d31--