Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93999
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender)
To: Alexander Lisachenko <lisachenko.it@gmail.com>,
 PHP internals list <internals@lists.php.net>
References: <CAEbg-4Y=DaJogK+EO8dH2x59Ak_vugwXxm4M4hPw4sgtSNqmug@mail.gmail.com>
Message-ID: <2f5d1f3b-c6db-fe83-e821-8e0d8bba603e@gmx.de>
Date: Wed, 15 Jun 2016 12:52:05 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <CAEbg-4Y=DaJogK+EO8dH2x59Ak_vugwXxm4M4hPw4sgtSNqmug@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: Throwing an Error for require expressions in PHP7.x
From: cmbecker69@gmx.de (Christoph Becker)

On 15.06.2016 at 12:27, Alexander Lisachenko wrote:

> For PHP7 we have pretty errors for almost everything, even eval can throw a
> ParseError exception, but not for the require expression, because it's
> still producing an uncatchable fatal errors:
> 
> try {
>     require('no.php');
> } catch (Throwable $e) {
>     echo 'Catch!';
> } finally {
>     echo 'Finally?';
> }
> // Warning: require(no.php): failed to open stream: No such file or
> directory
> // Fatal error: require(): Failed opening required 'no.php'
> 
> See https://3v4l.org/sQeAQ for live demo. What are the reasons not to throw
> Error here? Looks like an oversight for me.

This had recently been reported as feature request, and my reply was:

| With regard to your example: if a file is *required* and it can't
| be included, it doesn't make much sense to go on. If on the other
| hand the file is not really required, just `include` it.

[1] <https://bugs.php.net/72089>

-- 
Christoph M. Becker