Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61475
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
Date: Thu, 19 Jul 2012 18:54:56 +0800
To: Rune Kaagaard <rumi.kg@gmail.com>
Cc: Peter Beverloo <peter@lvp-media.com>, Rafael Dohms
 <listas@rafaeldohms.com.br>, Charlie Somerville
 <charlie@charliesomerville.com>, ivan.enderlin@hoa-project.net, 
 internals@lists.php.net
Message-ID: <36467402DA0F4332A523162E3C278042@gmail.com>
In-Reply-To: <CACMhqDFWv0-e_GSe24XnHNzAmmmfVsMwDxBEZFsL7D7i-EvgAQ@mail.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>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5007e780_77ae35eb_1060e"
Subject: =?utf-8?Q?=E5=9B=9E=E5=A4=8D=EF=BC=9A_?=[PHP-DEV] Make
 try/catch brackets optinal
From: reeze.xia@gmail.com (Reeze)

--5007e780_77ae35eb_1060e
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi=EF=BC=8C


=E5=9C=A8 2012=E5=B9=B47=E6=9C=8819=E6=97=A5=E6=98=9F=E6=9C=9F=E5=9B=9B=EF=
=BC=8C=E4=B8=8B=E5=8D=886:45=EF=BC=8CRune Kaagaard =E5=86=99=E9=81=93=EF=BC=
=9A

> +1 for the consistency of it. It's surprising that:
> =20
> if (=24foo)
> return =24bar;
> else
> return 42;
> =20
> works and:
> =20
> try
> maybe=5Fdangerous();
> catch(Dynamite =24e)
> handle=5Ferror();
> =20
> =20

There is no condition after =60try=60, it's really hard to read without b=
racket. =20
it becomes even worse if it didn't format pretty as above.
> does not.
> =20
> On Thu, Jul 19, 2012 at 12:11 PM, Peter Beverloo <peter=40lvp-media.com=
 (mailto:peter=40lvp-media.com)> wrote:
> > On Thu, Jul 19, 2012 at 11:06 AM, Rafael Dohms <listas=40rafaeldohms.=
com.br (mailto:listas=40rafaeldohms.com.br)>wrote:
> > =20
> > > On Thu, Jul 19, 2012 at 12:03 PM, Charlie Somerville <
> > > charlie=40charliesomerville.com (mailto:charlie=40charliesomerville=
.com)> wrote:
> > > =20
> > > > This has code readability problem written all over it. When maint=
aining
> > > it
> > > > also has problems, like with the bracket-less if's.
> > > > You would need to add brackets if you add an extra line here, as =
well as
> > > > you might get unexpected behaviour of you forget to
> > > > add brackets in that case.
> > > > =20
> > > > I've often heard people make this argument, but I've never found =
it to be
> > > > a real concern in practise.
> > > > =20
> > > > Is this really such a common problem=3F
> > > =20
> > > I have seen this problem happen, people losing time trying to figur=
e out
> > > what is wrong only to find
> > > its a missing bracket.
> > > As Paul said, this is bug-prone.
> > > =20
> > =20
> > =20
> > Other bracket-less blocks allow authors to shoot themselves in the fo=
ot
> > equally so, yet PHP supports these as well. The actual problem here i=
s an
> > inconsistency in the parser, which I'd consider to be a bug.
> > =20
> > Peter
> > =20
> > =20
> > > --
> > > Rafael Dohms
> > > PHP Evangelist and Community Leader
> > > http://www.rafaeldohms.com.br
> > > http://www.phpsp.org.br
> > > =20
> > =20
> > =20
> =20
> =20
> -- =20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
> =20
> =20



--5007e780_77ae35eb_1060e--