Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59339
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.170 as permitted sender)
Date: Tue, 3 Apr 2012 15:28:29 +0800
To: Rasmus Schultz <rasmus@mindplay.dk>
Cc: internals@lists.php.net
Message-ID: <2FD77C3003DC4656BCF6309B097DD978@gmail.com>
In-Reply-To: <CADqTB_i0yEgnqiOVbRLteA4rrdTuH1x-wNyEi2wQf0XnvrY9Hg@mail.gmail.com>
References: <CADqTB_i0yEgnqiOVbRLteA4rrdTuH1x-wNyEi2wQf0XnvrY9Hg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4f7aa69d_5b25ace2_be4d"
Subject: =?utf-8?Q?=E5=9B=9E=E5=A4=8D=EF=BC=9A_?=[PHP-DEV] resume after
 exception
From: reeze.xia@gmail.com (reeze)

--4f7aa69d_5b25ace2_be4d
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

If just for exception recovery how about implement ruby's retry =3F =20

http://www.tutorialspoint.com/ruby/ruby=5Floops.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=23 5.0, and =
while
> this has no particular relevance to PHP as such, it got me thinking abo=
ut
> this idea...
> =20
> What if you could resume execution after an exception was thrown=3F
> =20
> =46ictive example:
> =20
> function test()
> =7B
>  echo =22Begin Test=21=5Cn=22;
> =20
>  throw new Interrupt();
> =20
>  echo =22Execution resumed=21=22;
> =7D
> =20
> try
> =7B
>  test();
> =7D
> catch (Interrupt =24e)
> =7B
>  echo =22Execution interrupted.=5Cn=22;
>  resume;
> =7D
> =20
> The output of this would be:
> =20
> Begin Test=21
> Execution interrupted.
> Execution resumed=21
> =20
> In other words, Interrupt is a new type of Exception, from which you ca=
n
> recover, using the new resume keyword.
> =20
> Taking this one step further, imagine it were also possible to serializ=
e()
> 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.
> =20
> 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 :-)
> =20
> Any thoughts=3F


--4f7aa69d_5b25ace2_be4d--