Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69200
Return-Path: <patrick.allaert@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 2827 invoked from network); 18 Sep 2013 14:53:22 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 18 Sep 2013 14:53:22 -0000
Authentication-Results: pb1.pair.com header.from=patrick.allaert@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=patrick.allaert@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.52 as permitted sender)
X-PHP-List-Original-Sender: patrick.allaert@gmail.com
X-Host-Fingerprint: 74.125.83.52 mail-ee0-f52.google.com  
Received: from [74.125.83.52] ([74.125.83.52:42543] helo=mail-ee0-f52.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id CF/40-01324-16EB9325 for <internals@lists.php.net>; Wed, 18 Sep 2013 10:53:21 -0400
Received: by mail-ee0-f52.google.com with SMTP id c41so3468828eek.25
        for <internals@lists.php.net>; Wed, 18 Sep 2013 07:53:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:cc:content-type;
        bh=5DJyQKxiztx9kCHH34HXOxzJMq9PktkT4x0X9IkcVgM=;
        b=aiebz4aOQIz9Sk0DaaVi/AblR4I7Rb4RwCT53p8ucqJRRDxR8C51tWtDCZ2qp3vWbX
         xNvSN3A1z24cSpu9/xf8EjozAYJzVOggQchp/HY4ESeiK7vNECbzTnKv7Vp6Ltc6zXYS
         CsPcIyQtOCHsXLjmK7UsfO5PaZicd/PgPXgEb5m0o58p6BmyPpq8lmTm6yZRq3oZ3RNW
         KLeKbLQ/t7UdQZ9u/1wFINYXga08kWRpoaCP6lZ1xMqDwoikt4VHVxCUT1/a3mu5WFwJ
         B+VsrmRlk1PFvHyyXVMHm7Ja/8W5WnEYBLbM9185Yxh3ecfjRQMSl5YJVYAo+8j1MygH
         oHvA==
MIME-Version: 1.0
X-Received: by 10.15.111.132 with SMTP id cj4mr3969154eeb.56.1379515998747;
 Wed, 18 Sep 2013 07:53:18 -0700 (PDT)
Sender: patrick.allaert@gmail.com
Received: by 10.14.144.66 with HTTP; Wed, 18 Sep 2013 07:53:18 -0700 (PDT)
In-Reply-To: <CAAjMSDNwmpFRpX4VTj-AoUYp2PWXioyQRE3o8eCvb8VzXsB9Hw@mail.gmail.com>
References: <CAPwsocGni4kjJq9c5wr77ohPU+YX2=0O7EgahdH=p0=hH1H_fA@mail.gmail.com>
	<49D57F66323040FC9AE48244DAAF3771@gmail.com>
	<012B9378-3C3A-4169-96D3-3B57D6C7A82C@seancoates.com>
	<CAAjMSDNwmpFRpX4VTj-AoUYp2PWXioyQRE3o8eCvb8VzXsB9Hw@mail.gmail.com>
Date: Wed, 18 Sep 2013 16:53:18 +0200
X-Google-Sender-Auth: NXBdwsLB_dnbrLigpDsOM8heSaw
Message-ID: <CACwt+JcwJQB6b8JpJAp6g67NKgUr9ebMRbGKH=aHLX7wk+2Rxw@mail.gmail.com>
To: Chris London <me@chrislondon.co>
Cc: Sean Coates <sean@seancoates.com>, Leigh <leight@gmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Re: Allowing is_* functions to accept multiple parameters
From: patrickallaert@php.net (Patrick ALLAERT)

2013/9/18 Chris London <me@chrislondon.co>:
> I like the naming convention of are_*.  For me personally it isn't directly
> intuitive that the multiple parameters of is_* would be compared with an &&
> and not an ||.

isset() already operates that way, keeping "is_" and implementing it
as originally proposed by Leigh would, at least, be consistent.

[Derick mode: on]
PS: top posting is not #cool.