Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127222
Precedence: bulk
MIME-Version: 1.0
References: <39597a9c-6854-40c6-a529-32b2b178cb27@app.fastmail.com>
 <CAMW7n8CNTwOtsUbAbH-0Kk1Ck3DZ1fKF=P9GfctwDk9KmCr2XQ@mail.gmail.com>
 <ded712fb-b339-4160-8625-0f778a9c3926@app.fastmail.com> <CAMW7n8C1B68YU-369vjW1ui2iq1KS+kVE0m=hDdAiHSV-FKhJw@mail.gmail.com>
 <1748435831.865240.1745844029113@email.ionos.de>
In-Reply-To: <1748435831.865240.1745844029113@email.ionos.de>
Date: Mon, 28 Apr 2025 16:22:47 +0300
Message-ID: <CAMW7n8DjkLAXHomc4ZkK9uGEDEYf2TKCx+76G+y05RR+o-aCmw@mail.gmail.com>
Subject: Re: [PHP-DEV] Concept: Lightweight error channels
To: Thomas Bley <mails@thomasbley.de>
Cc: Larry Garfield <larry@garfieldtech.com>, php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000011e5400633d6954d"
From: edmond.ht@gmail.com (Edmond Dantes)

--00000000000011e5400633d6954d
Content-Type: text/plain; charset="UTF-8"

> 3) Implement a new LightException (or similar name) with no args in
getTrace().

+ or 4)  Deferred backtrace mechanism:

1. Does not compute the backtrace when the exception is created.
2. The backtrace is fully computed only if the exception is caught using a
catch block or by a global handler when reaching the bottom of the stack.
3. The backtrace may not be computed at all if the exception is caught for
suppression (possibly requiring separate syntax).

There is a technical problem here.
When a user saves an exception object somewhere and later tries to retrieve
the trace.
If a solution to this can be found, then no changes would be needed on the
UserLand side at all. ...

>

--00000000000011e5400633d6954d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">&gt; 3) Implement a new LightException (o=
r similar name) with no args in getTrace().</div><div dir=3D"ltr"><br></div=
><div dir=3D"ltr">+ or 4)=C2=A0

Deferred backtrace mechanism:

<br></div><div><br></div><div>1. Does not compute the backtrace when the ex=
ception is created.<br>
2. The backtrace is fully computed only if the exception is caught using a =
<code>catch</code> block or by a global handler when reaching the bottom of=
 the stack.<br>
3. The backtrace may not be computed at all if the exception is caught for =
suppression (possibly requiring separate syntax).=C2=A0=C2=A0</div><div><br=
></div><div>There is a technical problem here.<br>
When a user saves an exception object somewhere and later tries to retrieve=
 the trace.<br>
If a solution to this can be found, then no changes would be needed on the =
UserLand side at all. ...</div><div class=3D"gmail_quote gmail_quote_contai=
ner"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
 </div>
</blockquote></div></div>

--00000000000011e5400633d6954d--