Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67168
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAMUwpuTUVhZ23kCz8C0abU9FDzxrAat6y8mbOFKTd8gVifUV1Q@mail.gmail.com>
References: <CAMUwpuTUVhZ23kCz8C0abU9FDzxrAat6y8mbOFKTd8gVifUV1Q@mail.gmail.com>
Date: Fri, 26 Apr 2013 21:46:05 +0700
Message-ID: <CAAMrh8qWGsNzu3X55yaW+CVcTMwAi5=TG17jytkvyntrVikwNQ@mail.gmail.com>
To: Julien Pauli <jpauli@php.net>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=047d7b10c989451f1604db4498c2
Subject: Re: [PHP-DEV] Continued try blocks
From: syragg@gmail.com (=?KOI8-R?B?4czFy9PBzsTSIOLPwtLP1w==?=)

--047d7b10c989451f1604db4498c2
Content-Type: text/plain; charset=ISO-8859-1

Sounds interesting. And what about the second attempt passing the try block
without goto?


2013/4/26 Julien Pauli <jpauli@php.net>

> 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
>

--047d7b10c989451f1604db4498c2--