Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69180
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.177 as permitted sender)
MIME-Version: 1.0
Date: Wed, 18 Sep 2013 10:53:40 +0100
Message-ID: <CAPwsocGni4kjJq9c5wr77ohPU+YX2=0O7EgahdH=p0=hH1H_fA@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=f46d043be1e07f630c04e6a56933
Subject: Allowing is_* functions to accept multiple parameters
From: leight@gmail.com (Leigh)

--f46d043be1e07f630c04e6a56933
Content-Type: text/plain; charset=ISO-8859-1

Hi Internals.

How do you feel about expanding the is_* functions to accept multiple
parameters similar to the way isset() already does?

From the manual: "If multiple parameters are supplied then isset() will
return TRUE only if all of the parameters are set. Evaluation goes from
left to right and stops as soon as an unset variable is encountered."

I am proposing that all of the is_* functions are allowed to take a
variable number of parameters and will return true if all of the arguments
satisfy what is being checked.

i.e. is_null($a, $b, $c) would be the same as  is_null($a) && is_null($b)
&& is_null($c)

As well as producing much more succinct code and less function call
overhead, I think this ties in nicely with the variadic and unpacking RFCs
and is especially useful for parameters that cannot be typehinted; for
example you would be able to something like:

function doStuffWithNumbers(...$numbers) {
    if (!is_int(...$numbers)) {
        throw new InvalidArgumentException('blah');
...

Thoughts?

--f46d043be1e07f630c04e6a56933--