finally block of exception handling

Question

1.31/5 (6 votes)

See more:

C#

can we use return statement in finally block of exception handling..

Posted 18-Sep-12 9:08am

siddharth629

Updated 6-Nov-16 18:35pm

Add a Solution

Comments

[no name] 18-Sep-12 15:10pm

Working on your homework or sitting in an exam and trying to get the answers?

siddharth629 28-Sep-12 6:19am

sorry

Richard C Bishop 18-Sep-12 15:10pm

Have you tried it yet?

JOHN 602 18-Sep-12 15:15pm

Wes Aday, nice answer ahah

Herman<T>.Instance 18-Sep-12 15:18pm

yes you can but you can get the message that not all codepaths return a value

[no name] 18-Sep-12 15:35pm

I wish I could get 5!

Sergey Alexandrovich Kryukov 18-Sep-12 16:23pm

This is the answer of the type "yes, you can but you you cannot".

This resembles the well known joke (and actually, not even very much of a joke) on discussion of the shaky grounds of human right:

--"Do I have a right..?"
--"Yes, you have!"
--"So, can I?.."
--"No, you cannot".

:-)
--SA

[no name] 18-Sep-12 16:25pm

:-)

Sergey Alexandrovich Kryukov 18-Sep-12 16:27pm

Actually please see my comment to the comment by Wes, below. I suspect this error message is not so reasonable...
--SA

[no name] 18-Sep-12 15:36pm

Not in VS 2008 you can't, "Error 5 Control cannot leave the body of a finally clause"

Sergey Alexandrovich Kryukov 18-Sep-12 16:26pm

This rule is simply a safeguard against the case when some important (such as clean-up) statements comes after "return". If tend to think that this is excessive, because "unreachable code detected" would do the job, and return inside "finally" could make the code shorter, if the methods returns some value (non-void).
--SA

[no name] 18-Sep-12 16:29pm

Yes and it's actually a compiler error, http://msdn.microsoft.com/en-us/library/0hbbzekw.aspx

Sergey Alexandrovich Kryukov 18-Sep-12 17:15pm

Yes, I know. I just doubt it's reasonable.
--SA

[no name] 18-Sep-12 17:18pm

You would have to take that up with Anders Hejlsberg :-)

Sergey Alexandrovich Kryukov 18-Sep-12 17:28pm

Yes, this is not the only thing I would complain about. I can see at least 2 major failures of .NET, not counting problems in the architecture of some libraries.
--SA

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sangramsingh Pawar · Answer 1 · 2012-09-18T09:27:00

Solution 1

no we can't use return statement in finally block of exception handling.

Posted 18-Sep-12 9:27am

Sangramsingh Pawar

Member 12836013 · Answer 2 · 2016-11-06T18:35:00

Solution 3

We cannot use return statement in finally block.

Posted 6-Nov-16 18:35pm

Member 12836013

Comments

[no name] 8-Nov-16 16:03pm

Really? You mean that the solution 1 posted FOUR years ago saying the exact same thing was somehow unclear and you felt the need to say it again? Those worthless internet points must mean quite a lot to you.