Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59343
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain managedit.ie designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2FD77C3003DC4656BCF6309B097DD978@gmail.com>
References: <CADqTB_i0yEgnqiOVbRLteA4rrdTuH1x-wNyEi2wQf0XnvrY9Hg@mail.gmail.com>
	<2FD77C3003DC4656BCF6309B097DD978@gmail.com>
Date: Tue, 3 Apr 2012 10:53:33 +0100
Message-ID: <CAGSj+QuBCwgRAxXX-K6X3ppt-sea_cwySzgLqr+916cdV3AHZA@mail.gmail.com>
To: reeze <reeze.xia@gmail.com>
Cc: internals@lists.php.net, Rasmus Schultz <rasmus@mindplay.dk>
Content-Type: multipart/alternative; boundary=bcaec5196509b3943004bcc3471a
Subject: =?UTF-8?B?UmU6IFtQSFAtREVWXSDlm57lpI3vvJogW1BIUC1ERVZdIHJlc3VtZSBhZnRlciBleGNlcA==?=
	=?UTF-8?B?dGlvbg==?=
From: kiall@managedit.ie (Kiall Mac Innes)

--bcaec5196509b3943004bcc3471a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Retry is a feature I would very much like to see...

While it's not stritcly necessary to implement in core, it makes the code
much cleaner..

Thanks,
Kiall

Sent from my phone.
On Apr 3, 2012 8:28 a.m., "reeze" <reeze.xia@gmail.com> wrote:

> If just for exception recovery how about implement ruby's retry ?
>
> http://www.tutorialspoint.com/ruby/ruby_loops.htm  Ruby retry statement
> section.
>
>
>
> =E5=9C=A8 2012=E5=B9=B44=E6=9C=882=E6=97=A5=E6=98=9F=E6=9C=9F=E4=B8=80=EF=
=BC=8C=E4=B8=8B=E5=8D=888:44=EF=BC=8CRasmus Schultz =E5=86=99=E9=81=93=EF=
=BC=9A
>
> > I was just reading about the new async/await keywords in C# 5.0, and
> while
> > this has no particular relevance to PHP as such, it got me thinking abo=
ut
> > this idea...
> >
> > What if you could resume execution after an exception was thrown?
> >
> > Fictive example:
> >
> > function test()
> > {
> >  echo "Begin Test!\n";
> >
> >  throw new Interrupt();
> >
> >  echo "Execution resumed!";
> > }
> >
> > try
> > {
> >  test();
> > }
> > catch (Interrupt $e)
> > {
> >  echo "Execution interrupted.\n";
> >  resume;
> > }
> >
> > The output of this would be:
> >
> > Begin Test!
> > Execution interrupted.
> > Execution resumed!
> >
> > In other words, Interrupt is a new type of Exception, from which you ca=
n
> > recover, using the new resume keyword.
> >
> > Taking this one step further, imagine it were also possible to
> serialize()
> > an Interrupt - and resume it at a later time. This would open up entire=
ly
> > new possibilities for (AJAX) web-application frameworks, which would be
> > able to suspend execution, serialize the script state, return a respons=
e,
> > wait for further interaction from the user, and then resume execution.
> >
> > I'm sure there are lots of problems with this idea, and perhaps it's no=
t
> a
> > good fit for PHP at all, but I figured it couldn't harm to put the idea
> out
> > there anyway :-)
> >
> > Any thoughts?
>
>

--bcaec5196509b3943004bcc3471a--