Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100910
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <FA2F3B4D-F288-491F-B984-1ABA1CDFC945@gmail.com>
References: <CAEUnE0e6dS4QxoZB_Uy63cCwED1C2Hjan8zC8wPc+5zGcY2yzQ@mail.gmail.com>
 <46d05c00-c34a-a907-2eeb-07d424db71c6@gmx.de> <FA2F3B4D-F288-491F-B984-1ABA1CDFC945@gmail.com>
Date: Sat, 21 Oct 2017 14:17:34 -0400
Message-ID: <CAEUnE0fpZmFGH_WQOHph6DoXiARtO3-dY38ubgGsThzmmideRw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="94eb2c1285667b54d9055c129a25"
Subject: Re: [PHP-DEV] Re: Wouldn't Exception::getContext() be useful?
From: tendoaki@gmail.com (Michael Morris)

--94eb2c1285667b54d9055c129a25
Content-Type: text/plain; charset="UTF-8"

Just for debugging. I've been mulling over how to improve exception/error
handling in Drupal 8 out of the box.

On Sat, Oct 21, 2017 at 10:31 AM, Rowan Collins <rowan.collins@gmail.com>
wrote:

> On 21 October 2017 11:41:46 BST, "Christoph M. Becker" <cmbecker69@gmx.de>
> wrote:
> >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>.
>
>
> See also my posts about the problems of capturing arguments in the
> exception's backtrace (sorry, don't have an archive link to hand).
> Basically, holding references to objects without user interaction makes
> object lifetimes unpredictable and serialization unexpectedly fail.
>
> Did you just want this for debugging, or was there some other use case?
>
> Regards,
>
> --
> Rowan Collins
> [IMSoP]
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--94eb2c1285667b54d9055c129a25--