Re: Undestanding Exception Processing
- From: Maqsood Ahmed <maqsood_ahmed@xxxxxxxxx>
- Date: Tue, 26 Apr 2005 05:14:21 -0700
Answer 1: Following is the flow trace when an exception hasn't been
serviced in its original try/catch block and continue at the next catch
block.
i. Finally of original try/catch
(Optional) Finally of other try/catch blocks (up the stack) where
exception was not serviced
ii. Catch block where exception was serviced.
iii. Finally of the catch where exception was serviced.
Answer 2: Try/catch can not be looped unless you use labels (see: goto
statement). I personally think that it is not a good idea to loop a
try/catch. because if a statement fails once, it'll always fail to pass
try/catch.
I don't have much Idea about your third question.
HTH. Cheers :)
Maqsood Ahmed [MCP,C#]
Kolachi Advanced Technologies
http://www.kolachi.net
*** Sent via Developersdex http://www.developersdex.com ***
.
- Follow-Ups:
- Re: Undestanding Exception Processing
- From: gemel
- Re: Undestanding Exception Processing
- References:
- Undestanding Exception Processing
- From: gemel
- Undestanding Exception Processing
- Prev by Date: Re: New Column to DataSet.DataTable
- Next by Date: Estimate the Time for SQL query Execution
- Previous by thread: Undestanding Exception Processing
- Next by thread: Re: Undestanding Exception Processing
- Index(es):
Relevant Pages
|