Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61543
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.212.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAPaKmRnt5JPqYW_0umAdZvoCa=gY7cF12V8vH9NqJ5aDP43BSA@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>
	<36467402DA0F4332A523162E3C278042@gmail.com>
	<CAPaKmRnt5JPqYW_0umAdZvoCa=gY7cF12V8vH9NqJ5aDP43BSA@mail.gmail.com>
Date: Fri, 20 Jul 2012 08:47:51 +0100
Message-ID: <CAN+gjSdELv7PJM5hCC9wCxnN+mScNM0XcoGoAZWDTsVvwtcyNA@mail.gmail.com>
To: Amaury Bouchard <amaury@amaury.net>
Cc: internals@lists.php.net, Reeze <reeze.xia@gmail.com>
Content-Type: multipart/alternative; boundary=e0cb4efa789a015bbb04c53e1d10
Subject: =?UTF-8?B?UmU6IFtQSFAtREVWXSDlm57lpI3vvJogW1BIUC1ERVZdIE1ha2UgdHJ5L2NhdGNoIGJyYQ==?=
	=?UTF-8?B?Y2tldHMgb3B0aW5hbA==?=
From: ajfweb@googlemail.com (Andrew Faulds)

--e0cb4efa789a015bbb04c53e1d10
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I don't think we should add it purely for consistency, because then we'd
have to allow nonsense like:

switch x;
case 1;
endcase;
endswitch;

or...

try;
x;
catch e;
endtry;

Sure, consistency is good, but this would allow sloppy code.
On Jul 20, 2012 8:36 AM, "Amaury Bouchard" <amaury@amaury.net> wrote:

> 2012/7/19 Reeze <reeze.xia@gmail.com>
>
> > =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:
> > >
> > > if ($foo)
> > >   return $bar;
> > > else
> > >   return 42;
> > >
> > > works and:
> > >
> > > try
> > >   maybe_dangerous();
> > > catch(Dynamite $e)
> > >   handle_error();
> > >
> > >
> >
> > There is no condition after `try`, it's really hard to read without
> > bracket.
> > it becomes even worse if it didn't format pretty as above.
> >
>
> Bad argument. It's not about the presence of a condition after "try". It'=
s
> about language consistency.
> If you were right, we shouldn't be able to write that:
>   $i =3D 0;
>   do
>       echo($i++);
>   while ($i < 3);
>
> PHP allows it. Nobody cares about it, while I think it's a very ugly
> writing. But everybody is accustomed to it, because it's inherited from C
> syntax.
> And bracketless try/catch doesn't exists in other languages, so it
> shouldn't exists in PHP?
>
> More, do not confuse coding conventions (depends on people, changes from
> time to time) and language syntax (should be stable and consistent).
>

--e0cb4efa789a015bbb04c53e1d10--