Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53125
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain seld.be designates 209.85.214.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4DED5C77.8040209@sugarcrm.com>
References: <BANLkTimU6DxovPQFP6cOXE0sKTDchx5Ltg@mail.gmail.com>
	<4DED3A29.1090209@sugarcrm.com>
	<BANLkTimWtZOvu4LZAtpJsuZg1SXHdYYHxg@mail.gmail.com>
	<4DED43D4.4070006@sugarcrm.com>
	<DF.F3.23189.2B15DED4@pb1.pair.com>
	<4DED5C77.8040209@sugarcrm.com>
Date: Tue, 7 Jun 2011 12:09:17 +0200
Message-ID: <BANLkTimGjXNuDTpMdH7G+fzyQWsYKYJ6PA@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: "Matthew Weier O'Phinney" <weierophinney@php.net>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Callable typehint
From: j.boggiano@seld.be (Jordi Boggiano)

On Tue, Jun 7, 2011 at 1:02 AM, Stas Malyshev <smalyshev@sugarcrm.com> wrot=
e:
> Sure. How about reducing boilterplate code like this:
>
> if(is_readable($foo)) {
> =A0$var =3D file_get_contents($foo);
> } else {
> =A0throw =A0InvalidArgumentException();
> }
>
> Why won't we make language construct to do that too? I don't think these
> things belong in the language syntax.

The whole point is that callables are generally not constructed from
user input, they're hardcoded in the code somewhere, and so if a fatal
error occurs, the developer notices it, hopefully during development.

With is_readable, a file can be anywhere, anytime, readable or not, it
depends on the environment the code runs on, and not on the code
itself, so it's not deterministic and you should therefore be able to
easily handle this gracefully.

Cheers

--=20
Jordi Boggiano
@seldaek :: http://seld.be/