Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129294
Precedence: list
MIME-Version: 1.0
References: <CAEKnhAEO8w0GJXTVyH_nwK8nGQGdJcNNkGOPMnYDVrcsNGrm4A@mail.gmail.com>
In-Reply-To: <CAEKnhAEO8w0GJXTVyH_nwK8nGQGdJcNNkGOPMnYDVrcsNGrm4A@mail.gmail.com>
Date: Wed, 19 Nov 2025 10:42:06 +0100
Message-ID: <CANS-=pf=ggfWq7vF0shVinnH8NLQ-Z7sCJfx8Br36UJC5utgsA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Stream Error Handling Improvements
To: Jakub Zelenka <bukka@php.net>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003cbd7f0643ef6689"
From: kjarli@gmail.com (Lynn)

--0000000000003cbd7f0643ef6689
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 18, 2025 at 7:40=E2=80=AFPM Jakub Zelenka <bukka@php.net> wrote=
:

> Hello,
>
> I would like to introduce a new stream error handling RFC that is part of
> my stream evolution work (PHP Foundation project funded by Sovereign Tech
> Fund) :
>
> https://wiki.php.net/rfc/stream_errors
>
> Kind regards,
>
> Jakub
>
>
The naming of "terminal" is a little confusing to me. Reading the name with
a bool made me think it was whether or not the CLI was being used, which
made little sense in the context of stream errors. After reading the
explanation "Terminal errors are those that prevent an operation from
completing (e.g., file not found, permission denied). Non-terminal errors
are warnings or notices that don't stop execution (e.g., buffer
truncation).", I feel like it might be more clear if this property was
named after what the result is, perhaps something like "operationBlocked"
or "operationPrevented".

--0000000000003cbd7f0643ef6689
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 18,=
 2025 at 7:40=E2=80=AFPM Jakub Zelenka &lt;<a href=3D"mailto:bukka@php.net"=
>bukka@php.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div dir=3D"ltr">Hello,<br><br>I would like to introduce a ne=
w stream error handling RFC that is part of my stream evolution work (PHP F=
oundation project funded by Sovereign Tech Fund) :<br><br><a href=3D"https:=
//wiki.php.net/rfc/stream_errors" target=3D"_blank">https://wiki.php.net/rf=
c/stream_errors</a><br><br>Kind regards,<br><br>Jakub<div><br></div></div><=
/blockquote><div><br></div><div>The naming of &quot;terminal&quot; is a lit=
tle confusing to me. Reading the name with a bool made me think it was whet=
her or not the CLI was being used, which made little sense in the context o=
f stream errors. After reading the explanation &quot;Terminal errors are th=
ose that prevent an operation from completing (e.g., file not found, permis=
sion denied). Non-terminal errors are warnings or notices that don&#39;t st=
op execution (e.g., buffer truncation).&quot;, I feel like it might be more=
 clear if this property was named after what the result is, perhaps somethi=
ng like &quot;operationBlocked&quot; or &quot;operationPrevented&quot;.</di=
v></div></div>

--0000000000003cbd7f0643ef6689--