Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110272
To: internals@lists.php.net
References: <CAD2kNXAEjKW-VQC3PJUzBR9QTL=UEz=OGSTHNvee5tibDECN_Q@mail.gmail.com>
 <0819e254-c789-e3d6-b23d-08128f195953@gmail.com>
 <CAD2kNXBuJ-+EAPVNpm9VQXmD5GnjAKP7iveOyDSb3NXGkZCO6Q@mail.gmail.com>
Message-ID: <aae7117c-1685-79f0-374d-8b4c5284fc51@gmail.com>
Date: Mon, 25 May 2020 00:28:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <CAD2kNXBuJ-+EAPVNpm9VQXmD5GnjAKP7iveOyDSb3NXGkZCO6Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Error Exceptions mode
From: rowan.collins@gmail.com (Rowan Tommins)

On 24/05/2020 22:07, Katie Volz wrote:
> I hadn't thought putting the error types in the declare().  My only issue
> with that is how that would interact with the error_reporting setting - for
> example if I set my error_reporting to E_WARNING and error_exceptions to
> E_ALL I'm not sure whether a notice would be thrown.


In my mind error_reporting should make absolutely no difference. As you 
say, this option would be for people who don't want to interact with the 
current error system in any way, and that includes its global 
configuration state.


For instance, imagine you wrote this:

declare(error_exceptions=E_WARNING);
$fh = fopen($filePath, 'r');
// code using $fh


The point of using the declare here would be to avoid checking if $fh is 
false, since any errors opening the file would become exceptions. If 
error_reporting(0) can turn off that exception, you'll have to check for 
false anyway, defeating the purpose.


Regards,

-- 
Rowan Tommins (né Collins)
[IMSoP]