Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129722
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Precedence: list
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.300.41.1.7\))
Subject: Re: [PHP-DEV] [RFC] Stream Error Handling Improvements
Date: Tue, 30 Dec 2025 09:22:43 +0100
References: <CAEKnhAEO8w0GJXTVyH_nwK8nGQGdJcNNkGOPMnYDVrcsNGrm4A@mail.gmail.com>
 <CAEKnhAE5iG6VfgS6=+FrpbDN5T-7iOA7j0gN9n-pr0HmBe=3EA@mail.gmail.com>
To: PHP internals list <internals@lists.php.net>
In-Reply-To: <CAEKnhAE5iG6VfgS6=+FrpbDN5T-7iOA7j0gN9n-pr0HmBe=3EA@mail.gmail.com>
Message-ID: <7ECDE859-153C-4732-A3AB-716540489413@cschneid.com>
From: cschneid@cschneid.com (Christian Schneider)

Am 29.12.2025 um 19:52 schrieb Jakub Zelenka <bukka@php.net>:
> - The storing of errors is done at the end of the operation grouping =
and contains only the last grouped errors. So the function name was =
changed to stream_get_last_error(). It returns just a single StreamError =
which has a next property pointing to the next error if there is any.

I assume the chaining was based on Exception chaining but the example =
code under
	https://wiki.php.net/rfc/stream_errors#error_chaining
looks a bit clunky to me and I was wondering if returning an array of =
StreamError would not be more straightforward, i.e. one could then use =
foreach, empty(), count(), array_first(), array_last(), array_find() =
etc. instead of methods like while, $e->count(), $e->hasCode() which =
would make it feel more idiomatic to me.

But then again it might be a matter of taste and/or I might have missed =
something.

Regards,
- Chris