What's this meaning

Question

0.00/5 (No votes)

See more:

MSIL

Sub HandlerExample()
      Dim intX As Integer
      Dim intY As Integer
      Dim intZ As Integer
      intY = 0
      intX = 5
      ' First Required Error Statement.
      Try
          ' Cause a "Divide by Zero"
          intZ = CType((intX \ intY), Integer)
          ' Catch the error.
      Catch objA As System.DivideByZeroException
          Try
              Throw (New Exception("0 as divisor", objA))
          Catch objB As Exception
              Messagebox.Show(objB.Message)
              Messagebox.Show(objB.InnerException.Message)
              Messagebox.Show(objB.TargetSite.Name)
          End Try
      Catch
          Messagebox.Show("Caught any other errors")
      Finally
          Messagebox.Show(Str(intZ))
      End Try
  End Sub

The question is why we should use Try block inside another Try Block inside another one ...etc ??
I understand the base block but i don't know the others ?
Can you explain to me the the working of sub-Try Block ?

Posted 12-Nov-10 7:11am

Layth Rafea

Add a Solution

2 solutions

Solution 2

Hi,

It is explaining how you can catch different kinds of error with try catch.
In the first try catch, the programmer throw a DivideByZeroException exception. so it is catched on

Catch objA As System.DivideByZeroException.

( otherwise it is catched on

Catch        
 Messagebox.Show("Caught any other errors")

)

now in this catch (DevideByZeroException programmer throw another general exception. so it is catched in

Catch objB As Exception

The Finally block makes sure that the code

Messagebox.Show(Str(intZ))

will be executed.

Posted 12-Nov-10 7:30am

aidin Tajadod

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)

AspDotNetDev · Accepted Answer · 2010-11-12T07:20:00

Solution 1

There is sometimes a need for nested error handling. However, this particular case seems silly. There is no need for a nested Try/Catch in this scenario. You would need a nested Try/Catch if the code in the catch might throw an exception and you have a good reason to catch it.

Posted 12-Nov-10 7:20am

AspDotNetDev