Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67167
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.178 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
Date: Fri, 26 Apr 2013 16:41:17 +0200
Message-ID: <CAMUwpuTUVhZ23kCz8C0abU9FDzxrAat6y8mbOFKTd8gVifUV1Q@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0139ff308fc27f04db448973
Subject: Continued try blocks
From: jpauli@php.net (Julien Pauli)

--089e0139ff308fc27f04db448973
Content-Type: text/plain; charset=ISO-8859-1

Hello internals,

I had an idea recently with a friend, about a feature try-catch blocks
could use.
Let me just write an example, you will quickly understand the idea :

*<?php*
*
*
*try {*
*   foo();*
*   bar();*
*   baz();*
*} catch (SomeException $e) {*
*    dosomestuff();*
*    continue; /* Here is the feature, go back to try block */*
*} catch (Exception $e) {*
*    dosomething();*
*}*



The continue keyword would resume the execution from where it had
diverged, according to the function which led to the SomeException
catch block.

So, in this example, if, say, bar() throws a SomeException , the code
would then resume and execute baz() after the catch block.

Just presenting the idea here, no RFC actually , I'm collecting
thoughts and notices.

Julien.Pauli

--089e0139ff308fc27f04db448973--