Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110868
MIME-Version: 1.0
Date: Tue, 7 Jul 2020 22:46:56 +0200
Message-ID: <CABdc3WpEmoKTYEsDk+K1Jb=kh7nu8gJ3TkhY5639ueJaWjN9AQ@mail.gmail.com>
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003e414e05a9e018f7"
Subject: [RFC][DISCUSSION] debug_backtrace alternative as an array of
 StackFrame objects
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--0000000000003e414e05a9e018f7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=C5=82 Marcin Brzuchalski

--0000000000003e414e05a9e018f7--