Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100908
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: Michael Morris <tendoaki@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <CAEUnE0e6dS4QxoZB_Uy63cCwED1C2Hjan8zC8wPc+5zGcY2yzQ@mail.gmail.com>
Message-ID: <46d05c00-c34a-a907-2eeb-07d424db71c6@gmx.de>
Date: Sat, 21 Oct 2017 12:41:46 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAEUnE0e6dS4QxoZB_Uy63cCwED1C2Hjan8zC8wPc+5zGcY2yzQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: Wouldn't Exception::getContext() be useful?
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 21.10.2017 at 09:20, Michael Morris wrote:

> Right now the only way I know of to see the context of an exception throw
> is to pass it in..
> 
> throw new CustomException(get_definted_vars());
> 
> It would be very useful to have exceptions just have this as a method.
> set_error_handle had this ability, but it's now deprecated.  I'm guessing
> there's an engine reason why this hasn't happened because it seems like a
> pretty obvious include to the default methods of the Exception and Error
> objects.

Quite likely the same reasoning as for deprecating the $errcontext
argument applies, see
<https://wiki.php.net/rfc/deprecations_php_7_2#errcontext_argument_of_error_handler>.

-- 
Christoph M. Becker