try/catch/FINALLY View as Markdown

Hi all,

I know there was a lot of discussion about try/catch, but I will bring it up
again:

What about finally ?

I know someone posted that finally isn't necessary since PHP destroy all
variables and releases all resources at the end of the script. But if the
script is a PHP-GTK application or a standalone server aplication (like
CORBA)?

Finally is very useful in situations where you must be certain that some
piece of code will be executed no matter what happens (a normal execution, a
return statement or an exception).

IMHO I think that an implementation start would be hooking the function exit
at the engine..

Cristiano Duarte

The most important thing missing from this is that you cannot rethrow the
exception from the point where you suggest to place the finally code :-)

--Wez.

There's absolute no need for finally:

try {
}
catch (...) {
}
// here's you're finally code

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