Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:3757
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Wed, 6 Aug 2003 14:56:51 +0600
Reply-To: Simeon Koptelov <xi@newmail.ru>
Message-ID: <759544336.20030806145651@newmail.ru>
To: internals@lists.php.net
In-Reply-To: <85567616.20030806091410@post.rwth-aachen.de>
References: <20030806001540.7978.qmail@pb1.pair.com>
 <85567616.20030806091410@post.rwth-aachen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re[2]: [PHP-DEV] try/catch/FINALLY
From: xi@newmail.ru (Simeon Koptelov)

Hello Marcus,

Wednesday, August 6, 2003, 1:14:10 PM, you wrote:

CD>> What about finally ?

MB> There's absolute no need for finally:

MB> try {
MB> }
MB> catch (...) {
MB> }
MB> // here's you're finally code

try
{
   $this->allocateSomeResources();
   throw new SomeException();
}
catch( AnotherException $e )
{
}
finally
{
   $this->freeSomeResource();
}

This code will call freeSomeResource() -- that's why one may want to
have finally.

But I agree that there's no need for finally. If uncaught exception
is thrown -- it's bad application design or
malicious component( you cannot declare throws in function definition
so some evil component can do something like
" throw new ExceptionThatNobodyHandles(); // har-har-har!" .
You need to refactor in first case and
can do nothing in second -- if you'll start to free resources in
finally after each try-catch or always catch Exception,
your code will become garbage soon IMHO.

-- 
Best regards,
 Simeon                            mailto:xi@newmail.ru