Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103301
To: internals@lists.php.net
References: <CADqTB_j_FpODmfz38E3mXe7dLtH=JuyjOWZ=YZsCOsEEXYndKQ@mail.gmail.com>
Message-ID: <c6408299-7279-2a29-7c30-d6e8ff520c3b@gmail.com>
Date: Tue, 2 Oct 2018 22:37:29 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <CADqTB_j_FpODmfz38E3mXe7dLtH=JuyjOWZ=YZsCOsEEXYndKQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] deprecation of set_error_level() callback $errcontext
 argument
From: rowan.collins@gmail.com (Rowan Collins)

On 02/10/2018 15:57, Rasmus Schultz wrote:
> I understand the $errcontext argument to the set_error_level()
> callback was deprecated in 7.2.
>
> Apparently, this was deemed "not useful", but what's the alternative?


Digging into the archives, and the RFC [1], there was a bit more to it 
than "not useful"; capturing all variables in a local scope and making 
them available somewhere else is problematic when it comes to 
optimisation and analysis. This is particularly true since PHP has no 
way of making this data immutable, so any error can theoretically cause 
any local object to change state without being mentioned.

While I can understand the desire to have debugging feature built into 
the language "out of the box", it may be best left to extensions which 
can capture the information to a log or wherever without providing the 
full flexibility of the language to interact with it.

[1] 
https://wiki.php.net/rfc/deprecations_php_7_2#errcontext_argument_of_error_handler

Regards,

-- 
Rowan Collins
[IMSoP]