Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60909
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
Sender: tjerk.meesters@gmail.com
In-Reply-To: <CAGovj_M=nq3DzPh_vLL+C+ujAv0o+WqB7iRaj=OFLO2JOb7QgA@mail.gmail.com>
References: <CAGovj_M=nq3DzPh_vLL+C+ujAv0o+WqB7iRaj=OFLO2JOb7QgA@mail.gmail.com>
Date: Thu, 21 Jun 2012 11:17:21 +0800
Message-ID: <CAHMUw2GMxVoyFB3fcxfAETurBJUfcORR37r0HsqGGg+muicbaQ@mail.gmail.com>
To: Michael Morris <dmgx.michael@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Resume keyword
From: datibbaw@php.net (Tjerk Anne Meesters)

> Resume is similar to return, but can only be used in catch blocks or
> in error handling functions. =A0When encountered the run time returns to
> the line after the exception was initially thrown and, well,
> "resumes".

Interesting idea. Just by reading that I thought of this scenario instead:

---------------
try {
    echo "about to throw exception";
    throw new Exception;
    echo "still alive";
} catch (Exception $e) {
    resume;
}
-------------

Which kinda looks nice to have. But how about this:

--------------
function my_function()
{
    echo "throwing exception";
    throw new Exception;
    echo "still here?";
}

try {
    echo "calling function";
    my_function();
} catch (Exception $e) {
    resume;
}
----------------

By the time the exception is handled, the function stack would have
been unloaded, so how would it be able to resume? :)

>
> If resume has a value, and the exception was an assignment operation,
> then that value is assigned to the variable.

This feels a bit too magical IMO