Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61699
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.213.170 cause and error)
Message-ID: <500ED960.9020505@lerdorf.com>
Date: Tue, 24 Jul 2012 10:20:32 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Nikita Popov <nikita.ppv@gmail.com>
CC: Laruence <laruence@php.net>, PHP Internals <internals@lists.php.net>
References: <CABBJUpe-i3o5DcFH_cMJf7QxHmzkE3afjL_TXFrg-mCmOiFa=w@mail.gmail.com> <CAF+90c8xfpCmcMRiTqHrBQfPcHAotkpXfJKVskwycbdGB9R-UA@mail.gmail.com> <500EBC47.2080200@lerdorf.com> <CAF+90c9weB-xoODqoud83NbvvhxYMbRttPu6-YgxwfaMd4d8HQ@mail.gmail.com>
In-Reply-To: <CAF+90c9weB-xoODqoud83NbvvhxYMbRttPu6-YgxwfaMd4d8HQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Supports 'finally' keyword for PHP exceptions
From: rasmus@lerdorf.com (Rasmus Lerdorf)

On 07/24/2012 10:01 AM, Nikita Popov wrote:

> Another, separate point against finally is that in PHP (unlike many
> other languages) most (all?) built-in resources clean up after
> themselves. So if you open a file you don't have to worry about
> closing it again. It'll do that all by itself as soon as it goes out
> of scope. The same applies to database handles, etc. As PHP uses
> refcount based garbage collection the resource is actually cleaned up
> right away, not just at the next GC run (which could be problematic if
> you open up many files in a row).

Which is the argument for why finally doesn't need to worry about the
fatal-error case. Most resources are cleaned up on a fatal already,
including your lock example, so it isn't an issue. finally is
exception-level for intra-app cleanup, not for request shutdown cleanup.
We already have shutdown functions for that case.

-Rasmus