Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128430
Feedback-ID: ifab94697:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Fri, 08 Aug 2025 08:50:19 +0200
To: "Mihail Liahimov" <91liahim@gmail.com>,
 "Andreas Heigl" <andreas@heigl.org>
Cc: internals@lists.php.net
Message-ID: <e87e855c-fc18-4e70-90f1-6758dff96114@app.fastmail.com>
In-Reply-To: 
 <CAJWOiuPd67A7+CAhhHH538TaJGdgD3F0nK2tprCp-KOsk_nE1w@mail.gmail.com>
References: 
 <CAJWOiuN8fuejkX1Tj0h=s_Fs2bGEtz-qdMZxRTC1s4at23y=Vw@mail.gmail.com>
 <94a57a5c-41bc-442d-a5e3-13eaea29053b@app.fastmail.com>
 <CAJWOiuPaLfn+3Ez4JuOoOk2+OhUhasYxYkgKywntjj1Ew41AZQ@mail.gmail.com>
 <7acfc0ad-74a1-47c3-92cc-2f6c330bdb04@heigl.org>
 <CAJWOiuPd67A7+CAhhHH538TaJGdgD3F0nK2tprCp-KOsk_nE1w@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Optional Catch Block Body
Content-Type: multipart/alternative;
 boundary=c2cef1a02c15495f92b30117ce3072fe
From: rob@bottled.codes ("Rob Landers")

--c2cef1a02c15495f92b30117ce3072fe
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Fri, Aug 8, 2025, at 07:57, Mihail Liahimov wrote:
> Yeah, it seems to be problematic to use this syntax with finally block=
s. Perhaps the optional catch block should be allowed only at the very e=
nd, but it sounds somehow doubtful.
>=20
> =D1=81=D1=80, 6 =D0=B0=D0=B2=D0=B3. 2025=E2=80=AF=D0=B3. =D0=B2 16:52,=
 Andreas Heigl <andreas@heigl.org>:
>> Hey Mihail
>>=20
>> Am 06.08.25 um 13:34 schrieb Mihail Liahimov:
>> > Hi!
>> >=20
>> > At the moment, I can suggest this syntax:
>> >=20
>> > try {
>> > // do something
>> > } catch (SomeIgnorableException) finally {
>> > // do something
>> > }
>> >=20
>> I find that ... challenging
>>=20
>> When reading the code I now have to go to the end of the line to=20
>> understand that the second
>>=20
>> // do something
>>=20
>> does not belong to the `try` but to the `finally`...
>>=20
>>=20
>> And
>>=20
>> try {
>>    // break stuff
>> } catch (SomeIgnorableException)
>> finally {
>>    // do something regardless
>> }
>>=20
>> seems boken due to the missing }
>>=20
>> But well....
>>=20
>> We just have to adapt to something like this:
>>=20
>> try {
>>    // break stuff
>> }
>> catch (SomeIgnorableException)
>> catch (Some OtherIgnorableException)
>> finally {
>>    // do something regardless
>> }
>>=20
>> --=20
>>                                                                ,,,
>>                                                               (o o)
>> +---------------------------------------------------------ooO-(_)-Ooo=
-+
>> | Andreas Heigl                                                      =
 |
>> | mailto:andreas@heigl.org                  N 50=C2=B022'59.5" E 08=C2=
=B023'58" |
>> | https://andreas.heigl.org                                          =
 |
>> +--------------------------------------------------------------------=
-+
>> | https://hei.gl/appointmentwithandreas                              =
 |
>> +--------------------------------------------------------------------=
-+
>> | GPG-Key: https://hei.gl/keyandreasheiglorg                         =
 |
>> +--------------------------------------------------------------------=
-+

What about instead of at the end, we do it at the beginning?

try ignore (SomeIgnorableException, OtherException) {
  // break stuff
} catch(UnexpectedException) {
  // fix stuff
} finally {
  // do this anyway
}

Since ignore only can follow a try and any symbol other than a "{" is cu=
rrently an error, I don't think we don't need to reserve "ignore" as a k=
eyword.

It appears to be relatively easy to scan/read as well.

=E2=80=94 Rob
--c2cef1a02c15495f92b30117ce3072fe
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div>On Fri, Aug =
8, 2025, at 07:57, Mihail Liahimov wrote:</div><blockquote type=3D"cite"=
 id=3D"qt" style=3D""><div dir=3D"ltr"><div dir=3D"ltr">Yeah, it seems t=
o be problematic to use this syntax with finally blocks. Perhaps the opt=
ional catch block should be allowed only at the very end, but it sounds =
somehow doubtful.</div><div><br></div><div class=3D"qt-gmail_quote qt-gm=
ail_quote_container"><div dir=3D"ltr" class=3D"qt-gmail_attr">=D1=81=D1=80=
, 6 =D0=B0=D0=B2=D0=B3. 2025=E2=80=AF=D0=B3. =D0=B2 16:52, Andreas Heigl=
 &lt;<a href=3D"mailto:andreas@heigl.org">andreas@heigl.org</a>&gt;:</di=
v><blockquote class=3D"qt-gmail_quote" style=3D"margin-top:0px;margin-ri=
ght:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border=
-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;=
"><div>Hey Mihail</div><div> <br></div><div> Am 06.08.25 um 13:34 schrie=
b Mihail Liahimov:</div><div> &gt; Hi!</div><div> &gt; </div><div> &gt; =
At the moment, I can suggest this syntax:</div><div> &gt; </div><div> &g=
t; try {</div><div> &gt; // do something</div><div> &gt; } catch (SomeIg=
norableException) finally {</div><div> &gt; // do something</div><div> &=
gt; }</div><div> &gt; </div><div> I find that ... challenging</div><div>=
 <br></div><div> When reading the code I now have to go to the end of th=
e line to </div><div> understand that the second</div><div> <br></div><d=
iv> // do something</div><div> <br></div><div> does not belong to the `t=
ry` but to the `finally`...</div><div> <br></div><div> <br></div><div> A=
nd</div><div> <br></div><div> try {</div><div> &nbsp; &nbsp;// break stu=
ff</div><div> } catch (SomeIgnorableException)</div><div> finally {</div=
><div> &nbsp; &nbsp;// do something regardless</div><div> }</div><div> <=
br></div><div> seems boken due to the missing }</div><div> <br></div><di=
v> But well....</div><div> <br></div><div> We just have to adapt to some=
thing like this:</div><div> <br></div><div> try {</div><div> &nbsp; &nbs=
p;// break stuff</div><div> }</div><div> catch (SomeIgnorableException)<=
/div><div> catch (Some OtherIgnorableException)</div><div> finally {</di=
v><div> &nbsp; &nbsp;// do something regardless</div><div> }</div><div> =
<br></div><div> -- </div><div> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;,,,</div><div> &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (o o)</div><div> +=
---------------------------------------------------------ooO-(_)-Ooo-+</=
div><div> | Andreas Heigl&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;|</div><div> | mailto:<a href=3D"mailto:andreas@heigl.org" target=3D=
"_blank">andreas@heigl.org</a>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; N 50=C2=B022'59.5" E 08=C2=B023'58" |</div><div> | =
<a href=3D"https://andreas.heigl.org" rel=3D"noreferrer" target=3D"_blan=
k">https://andreas.heigl.org</a>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div><div> +-----------------=
----------------------------------------------------+</div><div> | <a hr=
ef=3D"https://hei.gl/appointmentwithandreas" rel=3D"noreferrer" target=3D=
"_blank">https://hei.gl/appointmentwithandreas</a>&nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp;|</div><div> +-----------------------------------------=
----------------------------+</div><div> | GPG-Key: <a href=3D"https://h=
ei.gl/keyandreasheiglorg" rel=3D"noreferrer" target=3D"_blank">https://h=
ei.gl/keyandreasheiglorg</a>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div><div> +-----------=
----------------------------------------------------------+</div></block=
quote></div></div></blockquote><div><br></div><div>What about instead of=
 at the end, we do it at the beginning?</div><div><br></div><div>try ign=
ore (SomeIgnorableException, OtherException) {</div><div>&nbsp; // break=
 stuff</div><div>} catch(UnexpectedException) {</div><div>&nbsp; // fix =
stuff</div><div>} finally {</div><div>&nbsp; // do this anyway</div><div=
>}</div><div><br></div><div>Since ignore only can follow a try and any s=
ymbol other than a "{" is currently an error, I don't think we don't nee=
d to reserve "ignore" as a keyword.</div><div><br></div><div>It appears =
to be relatively easy to scan/read as well.</div><div><br></div><div id=3D=
"sig121229152">=E2=80=94 Rob</div></body></html>
--c2cef1a02c15495f92b30117ce3072fe--