Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129719
Message-ID: <36066994-5b15-4b96-88db-47ab4bf92376@varteg.nz>
Date: Tue, 30 Dec 2025 12:22:52 +1300
Precedence: list
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Re: [RFC] Stream Error Handling Improvements
To: internals@lists.php.net
References: <CAEKnhAEO8w0GJXTVyH_nwK8nGQGdJcNNkGOPMnYDVrcsNGrm4A@mail.gmail.com>
 <CAEKnhAE5iG6VfgS6=+FrpbDN5T-7iOA7j0gN9n-pr0HmBe=3EA@mail.gmail.com>
Content-Language: en-GB
In-Reply-To: <CAEKnhAE5iG6VfgS6=+FrpbDN5T-7iOA7j0gN9n-pr0HmBe=3EA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: weedpacket@varteg.nz (Morgan)

On 2025-12-30 07:52, Jakub Zelenka wrote:
> 
>   Hi, I just published version 2.0 which is a significant redesign 
> including:
> 
> - Introducing ... StreamErrorCode 
> enums.... The 
> code is backed (int) because I need to keep the number to easily match 
> the category and simplify the mapping. I think that in this case a 
> backed enum is better.
> 

Just spitballing here, but perhaps a StreamErrorCategory enum? The Code 
could have a method/property that matches it to the corresponding 
Category; categorising errors of different kinds can be done by 
branching on the Category, rather than (possibly multiple) is*Error() tests.