Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61680
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAF+90c8xfpCmcMRiTqHrBQfPcHAotkpXfJKVskwycbdGB9R-UA@mail.gmail.com>
References: <CABBJUpe-i3o5DcFH_cMJf7QxHmzkE3afjL_TXFrg-mCmOiFa=w@mail.gmail.com>
	<CAF+90c8xfpCmcMRiTqHrBQfPcHAotkpXfJKVskwycbdGB9R-UA@mail.gmail.com>
Date: Tue, 24 Jul 2012 07:40:23 -0600
Message-ID: <CAFMT4Nrs_4aaXdc4t-TpDvkavgsKhPbDoX5aoNazGfxT_nCFYw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Laruence <laruence@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [RFC] Supports 'finally' keyword for PHP exceptions
From: morrison.levi@gmail.com (Levi Morrison)

On Tue, Jul 24, 2012 at 7:35 AM, Nikita Popov <nikita.ppv@gmail.com> 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).
> In particular this means that...
> ... if a die() is execute somewhere in the try clause (or a called
> function) the finally clause must still be run.
> ... if a parse error or other fatal error occurs in the try clause (or
> called function) the finally clause must still be run.
> ... if the user interrupts the process the finally clause must still be run.
>
> Basically this requires that all of the actions that are currently
> fatal need to be converted to exceptions. E.g. Python has special
> SystemExit and KeyboardInterrupt exceptions, as well as SyntaxError
> and so on.
>
> I obviously think that PHP should adopt this model too (as it gives
> the programmer more control), but until all fatal actions are turned
> into exceptions, I'm strongly against introducing "finally". The main
> point of the clause is to have a guarantee, and that is simply
> currently not present. You actually get a better guarantee if you just
> use destructors.
>
> Nikita
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

I definitely agree with Mr. Nikita Popov. Unless we have a
guarantee of `finally` running for PHP fatal errors, then this is not
particularly useful.