Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:3748
Return-Path: <cunha17@uol.com.br>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 17687 invoked by uid 1007); 6 Aug 2003 00:25:53 -0000
Message-ID: <20030806002553.17651.qmail@pb1.pair.com>
To: internals@lists.php.net
References: <20030806001540.7978.qmail@pb1.pair.com>
Date: Tue, 5 Aug 2003 21:25:52 -0300
Lines: 42
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Posted-By: 200.196.104.198
Subject: Re: try/catch/FINALLY
From: cunha17@uol.com.br ("Cristiano Duarte")

Please, ignore this:
> IMHO I think that an implementation start would be hooking the function
exit
> at the engine..

And read this instead:
IMHO I think that an implementation start would be hooking the exit of the
try statement even if its normal or has an exception thrown...

Best regards,

Cristiano Duarte

"Cristiano Duarte" <cunha17@uol.com.br> escreveu na mensagem
news:20030806001540.7978.qmail@pb1.pair.com...
> 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
>
>