Not sure if that's the proper term.

Let's say I have this:

function function1()
try
do something
function2()
catch
error
end try
end function


function function2()
try
do something
catch
error
end try
end function

When function 1 is called, will it abort if function 2 also aborts? Or will
function 1 do whatever it can regardless of whether function 2 aborts or
not?

-Darrel

"darrel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...

> When function 1 is called, will it abort if function 2 also aborts? Or
> will
> function 1 do whatever it can regardless of whether function 2 aborts or
> not?

What did you observe when you tried it for yourself...?

> What did you observe when you tried it for yourself...?

I'm not there yet...still building...will report back... ;o)

-Darrel

Good question darrel.

Exceptions "bubble up," which means that when an exception occurs, and is
not handled, it is passed to the calling function. So, if the calling
function doesn't handle it, it throws the same exception, which is then
passed to the function that called IT. And so on. So, whether the exception
bubbles up is determined by whether or not the exception is caught and
handled gracefully in the function in which it is thrown.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Everybody picks their nose,
But some people are better at hiding it.

"darrel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Not sure if that's the proper term.
>
> Let's say I have this:
>
> function function1()
> try
> do something
> function2()
> catch
> error
> end try
> end function
>
>
> function function2()
> try
> do something
> catch
> error
> end try
> end function
>
> When function 1 is called, will it abort if function 2 also aborts? Or
> will
> function 1 do whatever it can regardless of whether function 2 aborts or
> not?
>
> -Darrel
>
>
>

> Exceptions "bubble up," which means that when an exception occurs, and is
> not handled, it is passed to the calling function. So, if the calling
> function doesn't handle it, it throws the same exception, which is then
> passed to the function that called IT. And so on. So, whether the
exception
> bubbles up is determined by whether or not the exception is caught and
> handled gracefully in the function in which it is thrown.

Thanks, Kevin. That explains it nicely.

-Darrel