Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93997
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.51 as permitted sender)
To: internals@lists.php.net
References: <CAEbg-4Y=DaJogK+EO8dH2x59Ak_vugwXxm4M4hPw4sgtSNqmug@mail.gmail.com>
Message-ID: <945961b5-5875-0355-a55c-5c9bc734d6fd@gmail.com>
Date: Wed, 15 Jun 2016 11:39:02 +0100
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; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Throwing an Error for require expressions in PHP7.x
From: rowan.collins@gmail.com (Rowan Collins)

On 15/06/2016 11: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

Agree that this would be good. I don't know if there's a technical 
reason against it, or just that nobody's got round to it yet.


> Can we also add FileNotFoundException and use it for all file functions to
> avoid silencing with "@" operator?

This, however, is a completely different topic. It's one that's come up 
before, but not gained much traction, because it breaks an extremely 
large amount of existing code. I would suggest having a look in the list 
archives, and raising this as another topic if you can come up with a 
good plan for how it should work.

Regards,
-- 
Rowan Collins
[IMSoP]