Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69183
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain wiedler.ch from 217.26.49.174 cause and error)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
In-Reply-To: <CAPwsocGni4kjJq9c5wr77ohPU+YX2=0O7EgahdH=p0=hH1H_fA@mail.gmail.com>
Date: Wed, 18 Sep 2013 13:15:20 +0200
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <004CB360-7D96-411D-B8A2-C0E963EDCF7A@wiedler.ch>
References: <CAPwsocGni4kjJq9c5wr77ohPU+YX2=0O7EgahdH=p0=hH1H_fA@mail.gmail.com>
To: Leigh <leight@gmail.com>
Subject: Re: [PHP-DEV] Allowing is_* functions to accept multiple parameters
From: igor@wiedler.ch (Igor Wiedler)

On Sep 18, 2013, at 11:53 AM, Leigh <leight@gmail.com> wrote:

> Hi Internals.
>=20
> How do you feel about expanding the is_* functions to accept multiple
> parameters similar to the way isset() already does?
>=20
> ...
>=20
> Thoughts?

For isset() there is a good reason to do this, because the var might not =
exist at all, and as such you cannot use a function, as it would produce =
warnings.

However, for is_* functions, this could easily be done with a =
higher-order "every" function. You pass a predicate and an array of =
values. It returns a boolean.

Example:

	if (!every('is_int', $numbers)) {
		throw new \InvalidArgumentException(...);
	}

Not only is that much cleaner in my opinion, it also is composable =
without having to change *all* of the is_* predicates.

As such, I don't see much value in changing this.

Igor