It's quite hard to think of a compelling example. Usually you just
write the code and realize that "Yea, a 'finally' statement would make
a lot of sense here".
I believe it's the kind of functionality that you learn to use in
time, just like __set, __get, __sleep, __wakeup. If first two are no
brainier these days, the last two to me where "wtf? does anyone use
that? Where I need them at all?!". It was like that for 3-4 years.
Until I got the code witch actually made an active use of these two
and I understood the purpose.
Same goes to finally. I remember using in JavaScript a few times, helped a lot.
And it just makes sense to add to complete the try {} catch {} finally
{} template.
My 2 cents.
2012/2/28 Richard Lynch <c...@l-i-e.com>:
> On Tue, February 28, 2012 8:22 am, Kiall Mac Innes wrote:
>> +1000
>>
>> This is a feature that I've always wanted in PHP, My main reason being
>> to
>> reduce code duplication. eg
>>
>> try {
>> $fh = fopen($filename);
>>
>> // Do some work on the file + encounter an error.
>> throw new Exception();
>> } catch (Exception $e) {
>> // Log an error or something
> + if ($fh) fclose($fh); //many PHP file errors NULL out the $fh
> + }
> - > } finally {
> - > fclose($fh);
> - > }
>
> Another non-compelling example...
>
> Still not saying "finally" is a bad idea.
>
> Just want a compelling use case before I would vote...
>
> --
> brain cancer update:
> http://richardlynch.blogspot.com/search/label/brain%20tumor
> Donate:
> https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
