Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126137
Precedence: bulk
MIME-Version: 1.0
References: <CA+NMNO1zgCLLDOaWhqg8ipOrLETRn3w_91JNdCJz0zrKmeRWyg@mail.gmail.com>
 <87CA902B-E1CC-4D2F-8B78-0B15282EE8AA@gmail.com>
In-Reply-To: <87CA902B-E1CC-4D2F-8B78-0B15282EE8AA@gmail.com>
Reply-To: erictnorris@gmail.com
Date: Thu, 19 Dec 2024 09:24:37 -0500
Message-ID: <CA+NMNO1+q0ipPv-qGUJvxDd2NADHqEtH-ygg0abS-=AXwbkAXg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Error backtraces v2
To: Claude Pache <claude.pache@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: eric.t.norris@gmail.com (Eric Norris)

> Hi,
>
> Would be reasonable to be able to recover the stack trace of the error as a string, in addition to the proposed format? In general, it is the format I use in my error/exception handlers for convenience.
>
> A utility function that stringify the trace would be sufficient, as the operation is non-trivial.

It is reasonable to provide such a utility function, though I could
imagine some might argue that a function like that is better left to
userland libraries. In any case, I think I would prefer to leave that
for a future RFC in order to keep the scope of this one small.