Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93995
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.45 as permitted sender)
MIME-Version: 1.0
Date: Wed, 15 Jun 2016 13:27:56 +0300
Message-ID: <CAEbg-4Y=DaJogK+EO8dH2x59Ak_vugwXxm4M4hPw4sgtSNqmug@mail.gmail.com>
To: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11403be033560605354e9324
Subject: Throwing an Error for require expressions in PHP7.x
From: lisachenko.it@gmail.com (Alexander Lisachenko)

--001a11403be033560605354e9324
Content-Type: text/plain; charset=UTF-8

Hi, internals!

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.

Can we also add FileNotFoundException and use it for all file functions to
avoid silencing with "@" operator? Then require expression can throw an
Error with nested FileNotFoundException.

Thoughts?

--001a11403be033560605354e9324--