Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61552
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_34B59E1E-A7BA-4A73-A8E2-2DFF7F1CDBC8"; protocol="application/pgp-signature"; micalg=pgp-sha1
In-Reply-To: <500917C7.3050302@hoa-project.net>
Date: Fri, 20 Jul 2012 13:49:24 +0400
Cc: internals@lists.php.net
Message-ID: <3BF315E8-AF41-41F4-B1EA-16802BB07C50@gmail.com>
References: <5007D707.2070100@hoa-project.net> <CAOhuFvZMp4KXmkDm-uOwq6xxw5z3gfvwj1DhOjE29p+sVbKiew@mail.gmail.com> <095CAA408DA94AFB9E75C12877A9043D@charliesomerville.com> <CAOhuFvbEs5nZpYqUz7MpcjYFf+AkAb0S99CgP1pWFu-AquN07A@mail.gmail.com> <CAE8Xsdg9X_EWSbQ_WSRNBYoedtHcO_QeRGPp3jK4Spm7pwR=tw@mail.gmail.com> <CACMhqDFWv0-e_GSe24XnHNzAmmmfVsMwDxBEZFsL7D7i-EvgAQ@mail.gmail.com> <36467402DA0F4332A523162E3C278042@gmail.com> <CAPaKmRnt5JPqYW_0umAdZvoCa=gY7cF12V8vH9NqJ5aDP43BSA@mail.gmail.com> <CAN+gjSdELv7PJM5hCC9wCxnN+mScNM0XcoGoAZWDTsVvwtcyNA@mail.gmail.com> <500917C7.3050302@hoa-project.net>
To: ivan.enderlin@hoa-project.net
Subject: Re: [PHP-DEV] Make try/catch brackets optinal
From: indeyets@gmail.com (Alexey Zakhlestin)

--Apple-Mail=_34B59E1E-A7BA-4A73-A8E2-2DFF7F1CDBC8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On 20.07.2012, at 12:33, Ivan Enderlin @ Hoa wrote:

> Making braces optional for try/catch does:
> + not break backward compatibility;
> + add consistency in the PHP syntax;
> =B1 offer a new way to write buggy programs but no more than with =
other control structures (think about goto ;-)).
>=20
> I see more + than - here. Am I wrong?

You are not wrong. This is the inconsistency and it makes sense to fix =
it.
We are definitely not going to "unfix" it for if/else, so I "+1" your =
proposal in advance


> Moreover, in parallel, a new idea has been landing: introducing the =
=93rescue=94 keyword as a shortcut/replacement of try/catch, such as:
> $foo =3D callThatCouldThrow() rescue 'oof';
> Is it possible to chain it, such as:
> $foo =3D callThatCouldThrow() rescue anotherCallThatCouldThrow() =
rescue 'oof?';
>=20
> Maybe we should start another topic because it could be a nice idea.

I don't see value in this. "finally" would be much more valuable.

try {
    doSomething();
} catch (\Exception $e) {
    handleException();
} finally {
    genericCleanup() // called if everything is good, if everything is =
bad or even if exception is rethrown
}=

--Apple-Mail=_34B59E1E-A7BA-4A73-A8E2-2DFF7F1CDBC8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQEcBAEBAgAGBQJQCSmkAAoJEM8kLGy4PJ4JVRUIAM/WD94aWZGsHE5dEL+d9CU8
Ct6R1N2LtGdwzgvC0JV/072Am/y266Whzvl+CXHYeDw545b5oYpz5EqiVFrLTHHL
jdGxiYIXV65OT0m3sPC1ZU+rV6PwGBDgY6nH5jH3yhGSzwMylsD1MrbiIlRjAzdR
Pts05J1lBFggOtmcgYk0QwMab22S3y8Xwu7sDJyQT0WSij/lnXK1SVIAljDuD1Fp
4aTEvS58W/l16Le5fVovzp8wFECfPrSCj5pFNUcRprKf2nDp++zou7K5axNuFv/x
l9nJdr/HaMY3nYJvW1tZ101Rs5EGqAuwmcHNW47nHUggK/dA7masi7nHYFVsxCs=
=C2IC
-----END PGP SIGNATURE-----

--Apple-Mail=_34B59E1E-A7BA-4A73-A8E2-2DFF7F1CDBC8--