Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111309
MIME-Version: 1.0
References: <CABdc3Wpi0LB2aee_HbpRPJMKhOVLDTyrqp_rXOFDtkK8yhhOAQ@mail.gmail.com>
In-Reply-To: <CABdc3Wpi0LB2aee_HbpRPJMKhOVLDTyrqp_rXOFDtkK8yhhOAQ@mail.gmail.com>
Date: Tue, 4 Aug 2020 10:05:19 +0200
Message-ID: <CABdc3Wq4obfbKyF2nRmB4WVNEF4MgXZN0cDNGhKVgeYNn=MkCA@mail.gmail.com>
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000fc8be705ac08b718"
Subject: Re: [RFC][VOTE] debug_backtrace alternative as an array of StackFrame objects
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--000000000000fc8be705ac08b718
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Internals,

Voting has ended. The RFC was declined with 14 votes against and 14 votes
in favour.
The second vote shows we don't wanna change exceptions trace into objects
at all.

If I'm not wrong this means that debug_backtrace using objects as
frames instead of arrays has some potential and maybe it's worth to put it
as a PECL extension. Please correct me if I'm wrong.

Thanks for participating.

Cheers,
Micha=C5=82 Marcin Brzuchalski

wt., 21 lip 2020 o 13:52 Micha=C5=82 Marcin Brzuchalski <
michal.brzuchalski@gmail.com> napisa=C5=82(a):

> Hi Internals,
>
> I've opened the voting for adding object-based debug_backtrace()
> alternative.
> Secondary vote is about replacing object-based trace for
> Throwable::getTrace().
>
> Voting opened 2020-07-21 and closes 2020-08-04.
>
> Link to the RFC https://wiki.php.net/rfc/stack-frame-class#vote
>
> Cheers,
> Micha=C5=82 Marcin Brzuchalski
>

--000000000000fc8be705ac08b718--