Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61683
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: <500EA830.1040801@ajf.me>
Date: Tue, 24 Jul 2012 14:50:40 +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> <1343137723.2084.301.camel@guyrush>
In-Reply-To: <1343137723.2084.301.camel@guyrush>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] Supports 'finally' keyword for PHP exceptions
From: ajf@ajf.me (Andrew Faulds)

On 24/07/12 14:48, Johannes Schlüter wrote:
> 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
>
>
>
Tempfiles come to mind. Also, yes, PHP has destructors, but you are not 
always dealing with custom-made objects to handle this. And you may want 
something to happen before GC.