Will code after a Throw ever run?

[Jeff Johnson [MVP: VB]]

My testing seems to indicate that it won't, but no documentation I can find
explicitly states this. Let's say I throw a customer exception like this:

Try
m = New MyObject
Catch ex As Exception
Throw New MyObjectCreationFailedException(<stuff>)

LaunchNuclearMissiles()
End Try

Will the world ever get annihilated?

(I don't know WHY I thought I could put cleanup code after a Throw
statement, but I tried anyway and while stepping through in the debugger I
noticed that I was jumping out of the procedure as soon as the error was
thrown. Oops!)

[Charles Law]

Hi Jeff

Just one statement missing:

Try
m = New MyObject
Catch ex As Exception
Throw New MyObjectCreationFailedException(<stuff>)
Finally
LaunchNuclearMissiles()
End Try

HTH

Charles
"Jeff Johnson [MVP: VB]" <i.***@enough.spam> wrote in message
news:Ow**************@TK2MSFTNGP09.phx.gbl...

My testing seems to indicate that it won't, but no documentation I can find explicitly states this. Let's say I throw a customer exception like this:

Try
m = New MyObject
Catch ex As Exception
Throw New MyObjectCreationFailedException(<stuff>)

LaunchNuclearMissiles()
End Try

Will the world ever get annihilated?

(I don't know WHY I thought I could put cleanup code after a Throw
statement, but I tried anyway and while stepping through in the debugger I
noticed that I was jumping out of the procedure as soon as the error was
thrown. Oops!)

[Jeff Johnson [MVP: VB]]

"Charles Law" <bl**@thingummy.com> wrote in message
news:Oj**************@TK2MSFTNGP10.phx.gbl...

Just one statement missing:

Try
m = New MyObject
Catch ex As Exception
Throw New MyObjectCreationFailedException(<stuff>)
Finally
LaunchNuclearMissiles()
End Try

That wasn't what I was asking. I want to run cleanup code ONLY if an
exception occurs, and I wanted to know if using Throw absolutely, positively
exits a procedure without running any other statements that follow it
(Finally blocks notwithstanding; I know they're ALWAYS executed). Perhaps I
should have asked it as "Will any more code in a given Catch block run after
a Throw statement?"

[Charles Law]

Ah, yes, I see what you mean.

I would not expect any code to execute after the Throw. Could you not just
execute the clean-up in the Catch block, but before the Throw? Otherwise,
you would have to use a flag to select the code you want to run in the
Finally block.

Charles
"Jeff Johnson [MVP: VB]" <i.***@enough.spam> wrote in message
news:em**************@TK2MSFTNGP10.phx.gbl...

"Charles Law" <bl**@thingummy.com> wrote in message
news:Oj**************@TK2MSFTNGP10.phx.gbl...

Just one statement missing:

Try
m = New MyObject
Catch ex As Exception
Throw New MyObjectCreationFailedException(<stuff>)
Finally
LaunchNuclearMissiles()
End Try
That wasn't what I was asking. I want to run cleanup code ONLY if an
exception occurs, and I wanted to know if using Throw absolutely,

positively exits a procedure without running any other statements that follow it
(Finally blocks notwithstanding; I know they're ALWAYS executed). Perhaps I should have asked it as "Will any more code in a given Catch block run after a Throw statement?"

[Jeff Johnson [MVP: VB]]

"Charles Law" <bl**@thingummy.com> wrote in message
news:ub**************@TK2MSFTNGP09.phx.gbl...

Ah, yes, I see what you mean.

I would not expect any code to execute after the Throw. Could you not just
execute the clean-up in the Catch block, but before the Throw?

Yes, and I rearranged my code to do so. I just cannot find concrete
documentation that says that Throw forces (i.e., guarantees) an exit from a
procedure.

[Tom Shelton]

Jeff Johnson [MVP: VB] wrote:

"Charles Law" <bl**@thingummy.com> wrote in message
news:ub**************@TK2MSFTNGP09.phx.gbl...

Ah, yes, I see what you mean.

I would not expect any code to execute after the Throw. Could you not
just execute the clean-up in the Catch block, but before the Throw?

Yes, and I rearranged my code to do so. I just cannot find concrete
documentation that says that Throw forces (i.e., guarantees) an exit from
a procedure.

I'm not sure that it is explicitly stated in this manner, but since throwing
an exception causes an immediate search up the call stack for an error
handler, it is guarenteed for this to be the case... In other words,
control will be immediately passed to the next error handler.

Tom Shelton

[Jeff Johnson [MVP: VB]]

"Tom Shelton" <to*@mtogden.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

I'm not sure that it is explicitly stated in this manner, but since throwing an exception causes an immediate search up the call stack for an error
handler, it is guarenteed for this to be the case... In other words,
control will be immediately passed to the next error handler.

Right, that I've seen. I just want warm and fuzzies that searching for an
error handler isn't like calling a subroutine: i.e., that control WON'T
return to the statement after the Throw once the error has been handled. I'm
pretty sure it won't (since it hasn't yet), but it's the kind of thing that
should be stated in the docs.