Re: [RFC][DISCUSSION] debug_backtrace alternative as an array of StackFrame objects
| From: | Levi Morrison via internals | Date: | Wed, 08 Jul 2020 20:25:41 +0000 |
| Subject: | Re: [RFC][DISCUSSION] debug_backtrace alternative as an array of StackFrame objects | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-110885@lists.php.net to get a copy of this message | ||
On Tue, Jul 7, 2020 at 2:47 PM Michał Marcin Brzuchalski
<michal.brzuchalski@gmail.com> wrote:
>
> Hi internals,
>
> following recently added alternative to
token_get_all() in form
> of a
> dedicated class PhpToken
> I've made a similar proposal for collecting stack traces by introducing
> StackFrame::getTrace()
> and StackFrame which replaces array with keys and values known
> from
> debug_backtrace().
>
> To compete with easier adoption StackFrame implements
> ArrayAccess
> giving identical API
> to debug_backtrace().
>
> A test script with deep recursion up to 1M frames uses 50% less memory than
> debug_backtrace().
>
> The RFC is described here
> https://wiki.php.net/rfc/stack-frame-class
> It includes implementation of PoC and tests.
>
> Cheers,
> Michał Marcin Brzuchalski
Any opposition for a parameter to limit stack depth? It's something
I'd like on the old API too.