Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122330
MIME-Version: 1.0
References: <CAK=iT=UrMCPw5ydCnxa_87ws6xKRO5Y3qJnmchczgDds8u660A@mail.gmail.com>
 <CABigaAUjSx3-vEaQhPk-toJTSg+J3CLrO3otpm1g6hqbYyQKvw@mail.gmail.com>
 <CAK=iT=WgsEZjyu3Y2wTWvycqCsYH7MrLsZgERZK3u75U08ePpA@mail.gmail.com>
 <CAL0xaBHfEMs1BVAMZOuFCUpb9orNSRD0YDhu=3wJAGK7K0_=dg@mail.gmail.com>
 <CAK=iT=XDVcs+y4XDmGu2re137i2yD9LiEj1-HLvyxxxrb8jFUw@mail.gmail.com>
 <CAK=iT=UDUjCZ-25k_MkHFO7uKdWAqoJxdWLVBGM2_SYDk-JyAg@mail.gmail.com>
 <742f202d-7990-4f51-b903-7a15e3fd33c2@app.fastmail.com> <CAL0xaBFybT7F1J5fMZyz9JkeP79iVveCeFTRUFKzQgdgAPDYPQ@mail.gmail.com>
 <CAK=iT=W3pC5xXa8cMmqdTmog6bOC-oYo2csetQADYEUE3+yCZw@mail.gmail.com>
 <3db4fbe0-22f4-44e2-a1a6-6cd85287df56@app.fastmail.com> <CAPzBOBPKF6CSzVcuxq1Gz44uZKLJA6yJ73mTtVidYXXg0z0pYA@mail.gmail.com>
 <4fa06ed3-855a-4952-a1fe-c97c5249b814@app.fastmail.com> <CAK=iT=WBS4p2evgPPzaiX9ia3U-hHpa4vdvS4niQVo5K1d48Fg@mail.gmail.com>
In-Reply-To: <CAK=iT=WBS4p2evgPPzaiX9ia3U-hHpa4vdvS4niQVo5K1d48Fg@mail.gmail.com>
	=?UTF-8?B?Yg==?= <6562680@gmail.com>
Date: Wed, 7 Feb 2024 18:15:01 +0300
Message-ID: <CAK=iT=U4EOrfckuVypLPSs184uvgtxEJJZvcSPUbPohzGjn5YQ@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000cf5fe60610cc2ab3"
Subject: Re: [PHP-DEV] Feature request: https://github.com/php/php-src/issues/13301
From: 6562680@gmail.com (=?UTF-8?B?0JPRgNC40LPQvtGA0LjQuSBTZW5pb3IgUEhQIC8g0KDQsNC30YDQsNCx0L7RgtGH0LjQuiBXZQ==?==?UTF-8?B?Yg==?=)

--000000000000cf5fe60610cc2ab3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

As I mentioned above - javascript pipelines (named `Promise` and
`Thenable`) are great examples when exceptions are a bad choice. Btw, not
"bad", but "choice to stop one step of the chain only".

If any step of chain/foreach throws an exception - it will break all code.
Should break one step. That's why you throw the immediate catch. And
continue to check via if-checking once the result of the pipeline is
received.

Catching is a good solution for the application core. If some exception
pops up at the entrypoint - you could transform the exception to the
output. All other cases should be covered without exceptions. If you use
exceptions on any occurred error as "truth way" you will meet risk and also
timeloss on any misformatted batches/user-inputs.

=D1=81=D1=80, 7 =D1=84=D0=B5=D0=B2=D1=80. 2024=E2=80=AF=D0=B3. =D0=B2 18:06=
, =D0=93=D1=80=D0=B8=D0=B3=D0=BE=D1=80=D0=B8=D0=B9 Senior PHP / =D0=A0=D0=
=B0=D0=B7=D1=80=D0=B0=D0=B1=D0=BE=D1=82=D1=87=D0=B8=D0=BA Web <
6562680@gmail.com>:

> Analyzing the problem on a single level operation is incorrect. New code
> and simple operations are fully covered with exception/try/catch flow.
>
> The main point i tried to attract your attention is that if you working i=
n
> batches/queues/pipelines you still need errors collection, and if you mad=
e
> error flow with exceptions - you have to extract validations to separate
> classes/dto-s, made return types as objects, try/catching as fast as
> possible, and then you will still met errors from remote systems, network
> errors, and invalid response parsing that need to be logged as much close
> to task registration place.
>
> So correct analysis - providing an example with at least foreaches/yields
> instead of simply calling native functions. In small functions IF
> statements are overkill, and even try-catch could be skipped, because the
> whole script will fall and that's correct behavior.
>
> Case is in that the script should continue working while working with
> chaining/nesting, and should be able to easily refactor any step to skip
> one or more bulk-data rows of each step on any nesting level.
>


--=20
+375 (29) 676-48-68 <+375296764868> / Mobile - =D0=BF=D1=80=D0=B5=D0=B4=D0=
=BF=D0=BE=D1=87=D0=B8=D1=82=D0=B0=D0=B5=D0=BC=D1=8B=D0=B9 =D1=81=D0=BF=D0=
=BE=D1=81=D0=BE=D0=B1 =D1=81=D0=B2=D1=8F=D0=B7=D0=B8
https://t.me/gzhegow / https://t.me/%2B375296764868 / Telegram
6562680@gmail.com

--000000000000cf5fe60610cc2ab3--