try, catch, finally- whats the point of finally?

[Alan Paulk]

It seems to me if you have a function like this

public void blah()

try
{
blah blah;
}

catch
{
blah de blah;
}

#code that executes whether there is an error or not#

return;

Then the code at the end will execute just as if it were in a finally
block. If that is the case then I don't know what the point of a
finally block is. Couls someone clear that up for me?

-Alan

[Justin Rogers]

finally is a guarantee that the code will get run. Take this example:

try {

"Alan Paulk" <ap****@141.com > wrote in message
news:60******** *************** ***@posting.goo gle.com...

It seems to me if you have a function like this

public void blah()

try
{
blah blah;
}

catch
{
blah de blah;
}

#code that executes whether there is an error or not#

return;

Then the code at the end will execute just as if it were in a finally
block. If that is the case then I don't know what the point of a
finally block is. Couls someone clear that up for me?

-Alan

[Justin Rogers]

Darnit, sorry, the Ctrl+Enter bug hit again.

Take this code:

try {
// Throw your exception
} finally {
// Run your clean-up here
}

The exception will bubble up the call stack and get caught by
another catch block if one exists, but your finally code will still
get run. If you placed the code outside of the finally block, then
execution would stop at the exception and be thrown up the stack
to be caught. Let's take a resource allocation example.

try {
// My library accesses a stream
// Some error happens and I need to throw an exception for the user.
throw new Exception("Inva lid data was in the stream");
} finally {
// Close the stream here
}
--
Justin Rogers
DigiTec Web Consultants, LLC.
Blog: http://weblogs.asp.net/justin_rogers

"Alan Paulk" <ap****@141.com > wrote in message
news:60******** *************** ***@posting.goo gle.com...

It seems to me if you have a function like this

public void blah()

try
{
blah blah;
}

catch
{
blah de blah;
}

#code that executes whether there is an error or not#

return;

Then the code at the end will execute just as if it were in a finally
block. If that is the case then I don't know what the point of a
finally block is. Couls someone clear that up for me?

-Alan

[Hirantha]

Here's some good readings on it
http://www.jaggersoft.com/pubs/Excep...ngInCSharp.htm

--
hth
Hirantha
Please reply only to the newsgroups.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[astanley]

Also, code in a catch block gets called *only* if an exception is thrown. Code in a finally block gets called if an exception is thrown or if an exception is *not* thrown.

[Alan Paulk]

"Justin Rogers" <Ju****@games4d otnet.com> wrote in message news:<em******* *******@TK2MSFT NGP10.phx.gbl>. ..

Darnit, sorry, the Ctrl+Enter bug hit again.

Take this code:

try {
// Throw your exception
} finally {
// Run your clean-up here
}

The exception will bubble up the call stack and get caught by
another catch block if one exists, but your finally code will still
get run. If you placed the code outside of the finally block, then
execution would stop at the exception and be thrown up the stack
to be caught. Let's take a resource allocation example.

try {
// My library accesses a stream
// Some error happens and I need to throw an exception for the user.
throw new Exception("Inva lid data was in the stream");
} finally {
// Close the stream here
}
--
Justin Rogers
DigiTec Web Consultants, LLC.
Blog: http://weblogs.asp.net/justin_rogers

"Alan Paulk" <ap****@141.com > wrote in message
news:60******** *************** ***@posting.goo gle.com...

It seems to me if you have a function like this

public void blah()

try
{
blah blah;
}

catch
{
blah de blah;
}

#code that executes whether there is an error or not#

return;

Then the code at the end will execute just as if it were in a finally
block. If that is the case then I don't know what the point of a
finally block is. Couls someone clear that up for me?

-Alan

Thanks for the help!
-Alan

[The Real Andy]

On 4 May 2004 02:54:47 -0700, ap****@141.com (Alan Paulk) wrote:

"Justin Rogers" <Ju****@games4d otnet.com> wrote in message news:<em******* *******@TK2MSFT NGP10.phx.gbl>. ..

Darnit, sorry, the Ctrl+Enter bug hit again.

Take this code:

try {
// Throw your exception
} finally {
// Run your clean-up here
}

The exception will bubble up the call stack and get caught by
another catch block if one exists, but your finally code will still
get run. If you placed the code outside of the finally block, then
execution would stop at the exception and be thrown up the stack
to be caught. Let's take a resource allocation example.

try {
// My library accesses a stream
// Some error happens and I need to throw an exception for the user.
throw new Exception("Inva lid data was in the stream");
} finally {
// Close the stream here
}
--
Justin Rogers
DigiTec Web Consultants, LLC.
Blog: http://weblogs.asp.net/justin_rogers

"Alan Paulk" <ap****@141.com > wrote in message
news:60******** *************** ***@posting.goo gle.com...

> It seems to me if you have a function like this
>
> public void blah()
>
> try
> {
> blah blah;
> }
>
> catch
> {
> blah de blah;
> }
>
> #code that executes whether there is an error or not#
>
> return;
>
> Then the code at the end will execute just as if it were in a finally
> block. If that is the case then I don't know what the point of a
> finally block is. Couls someone clear that up for me?
>
> -Alan

Thanks for the help!
-Alan

Most C++ programmers (including myself!) think the finally clause is
an absolute godsend!

[Stu Smith]

(lots of snip)

Most C++ programmers (including myself!) think the finally clause is
an absolute godsend!

As far as I'm aware the reason that Stroustrup didn't put finally into C++
is because there is a much better idiom in that language: destruction of
stack-based objects.

C# (and .NET), which don't support deterministic finalization, needed an
alternative method of safely releasing resources etc.

Stu