Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61682
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Laruence <laruence@php.net>
Cc: PHP Internals <internals@lists.php.net>
In-Reply-To: <CABBJUpe-i3o5DcFH_cMJf7QxHmzkE3afjL_TXFrg-mCmOiFa=w@mail.gmail.com>
References:
	 <CABBJUpe-i3o5DcFH_cMJf7QxHmzkE3afjL_TXFrg-mCmOiFa=w@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 24 Jul 2012 15:48:43 +0200
Message-ID: <1343137723.2084.301.camel@guyrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Supports 'finally' keyword for PHP exceptions
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Tue, 2012-07-24 at 19:20 +0800, Laruence wrote:
> Hi:
>     As the previous threads disscussed,  I make a implemention.
> 
>     here is the RFC: https://wiki.php.net/rfc/finally
> 
>     any suggestions?
> 
> thanks

As PHP has destructors there is less need for "finally" compared to
other languages. What are the cases where an extra language construct is
needed? (i.e. one can also use C++-like RAII things ...)

The RFC is also missing to demonstrate the order of finally calls in
nested try-catch-blocks.

johannes