Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61690
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 64.22.89.133 as permitted sender)
Message-ID: <500EBC84.2030403@ajf.me>
Date: Tue, 24 Jul 2012 16:17:24 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: internals@lists.php.net
References: <CABBJUpe-i3o5DcFH_cMJf7QxHmzkE3afjL_TXFrg-mCmOiFa=w@mail.gmail.com> <CAF+90c8xfpCmcMRiTqHrBQfPcHAotkpXfJKVskwycbdGB9R-UA@mail.gmail.com> <500EBC47.2080200@lerdorf.com>
In-Reply-To: <500EBC47.2080200@lerdorf.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Supports 'finally' keyword for PHP exceptions
From: ajf@ajf.me (Andrew Faulds)

On 24/07/12 16:16, Rasmus Lerdorf wrote:
> On 07/24/2012 06:35 AM, Nikita Popov wrote:
>> On Tue, Jul 24, 2012 at 1:20 PM, Laruence <laruence@php.net> wrote:
>>> Hi:
>>>      As the previous threads disscussed,  I make a implemention.
>>>
>>>      here is the RFC: https://wiki.php.net/rfc/finally
>>>
>>>      any suggestions?
>> The finally clause comes with a very strong promise that the code in
>> the clause will run in absolutely any case (short of sigkill, maybe).
> No it doesn't, at least not in Java. A fatal Java error or an explicit
> call to System.exit() will cause the finally clause to not be executed.
> It is a simple exception-level construct and doesn't in any way promise
> to be called in a fatal error situation. And regardless of what Java
> does, we are free to define it and provide whatever promises we want
> here, but keeping it in line with Java's implementation makes sense to me.
>
> -Rasmus
>
Yeah, finally{} won't happen in absolutely any case. But if there's an 
exception that's uncaught it *should* still run.