Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59333
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain charliesomerville.com from 74.125.82.54 cause and error)
MIME-Version: 1.0
In-Reply-To: <CADqTB_i0yEgnqiOVbRLteA4rrdTuH1x-wNyEi2wQf0XnvrY9Hg@mail.gmail.com>
References: <CADqTB_i0yEgnqiOVbRLteA4rrdTuH1x-wNyEi2wQf0XnvrY9Hg@mail.gmail.com>
Date: Tue, 3 Apr 2012 08:43:00 +1000
Message-ID: <CAO8n+WJjsVM-af_ARp1XoQhvCgWTz8JsFZ10FpBW6iNChoMRUw@mail.gmail.com>
To: Rasmus Schultz <rasmus@mindplay.dk>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=f46d043892ab8d66a004bcb9e9c4
Subject: Re: [PHP-DEV] resume after exception
From: charlie@charliesomerville.com (Charlie Somerville)

--f46d043892ab8d66a004bcb9e9c4
Content-Type: text/plain; charset=UTF-8

Magnus Holm has an excellent proof of concept for this in Ruby, which
supports continuations:

http://timelessrepo.com/never-gonna-let-you-go
On Apr 2, 2012 10:44 PM, "Rasmus Schultz" <rasmus@mindplay.dk> wrote:

> 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 about
> 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 can
> 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 entirely
> new possibilities for (AJAX) web-application frameworks, which would be
> able to suspend execution, serialize the script state, return a response,
> 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 not a
> good fit for PHP at all, but I figured it couldn't harm to put the idea out
> there anyway :-)
>
> Any thoughts?
>

--f46d043892ab8d66a004bcb9e9c4--