Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60223
Return-Path: <florian@anderiasch.de>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 54823 invoked from network); 20 Apr 2012 06:03:21 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 20 Apr 2012 06:03:21 -0000
Authentication-Results: pb1.pair.com header.from=florian@anderiasch.de; sender-id=unknown
Authentication-Results: pb1.pair.com smtp.mail=florian@anderiasch.de; spf=permerror; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain anderiasch.de from 81.169.138.148 cause and error)
X-PHP-List-Original-Sender: florian@anderiasch.de
X-Host-Fingerprint: 81.169.138.148 ares.art-core.org Linux 2.5 (sometimes 2.4) (4)
Received: from [81.169.138.148] ([81.169.138.148:56135] helo=mail.anderiasch.de)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 82/67-18164-62CF09F4 for <internals@lists.php.net>; Fri, 20 Apr 2012 02:03:19 -0400
Message-ID: <4F90FC23.3000709@anderiasch.de>
Date: Fri, 20 Apr 2012 08:03:15 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.3) Gecko/20120329 Icedove/10.0.3
MIME-Version: 1.0
To: Stas Malyshev <smalyshev@sugarcrm.com>
CC: Nikita Popov <nikita.ppv@googlemail.com>, 
 Matthew Weier O'Phinney <weierophinney@php.net>,
 "internals@lists.php.net" <internals@lists.php.net>
References: <4F8DF4B1.2040307@sugarcrm.com> <C5.AB.03614.59EBE8F4@pb1.pair.com>	<4F8F2304.7090402@sugarcrm.com> <CAF+90c9iEXFKVWR+HGgbxOeyE7rjfMfzV6uksZkbstq2jn6yxQ@mail.gmail.com> <4F8F2C50.4080102@sugarcrm.com>
In-Reply-To: <4F8F2C50.4080102@sugarcrm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [RFC] skipping optional parameters
From: florian@anderiasch.de (Florian Anderiasch)

On 04/18/2012 11:04 PM, Stas Malyshev wrote:
> Hi!
> 
>> "default" is already a reserved keyword. It's used in switch
>> constructs. So it is safe to use :)
> 
> Ah, silly me, indeed it is. Then I guess it doesn't hurt to add it as an
> option. Will do.

I can't estimate the amount of breakage, but what about using underscore
(literal _) without quotation marks?

In functional languages it's sometimes the "default match" in pattern
matching, that's at least a loose conversion and I hope not many people
would do
define("_", <whatever>) in their code.

The question now is, if create_query("a", _, _, _, true) really looks
better...

Greetings,
Florian