Take the 2-minute tour ×  Been having a "heated debate" with a
colleague about his practice of wrapping most of his functions
in a try/catch but the catch has JUST a "throw" in it e.g.
Private sub foo()         'Do something'         throw 'And
nothing else!'     End Try End Sub  My thought was to not even
bother (assuming you don't need to do anything at this point) -
the exception would bubble to the next exception handler in a
parent member.  The only argument that sounded plausible was
that sometimes exceptions weren't caught and your code stopped
(in debug mode) with the current line highlighted in green...and
that this may be something to do with multiple threads? Best
practice does state "an exception handler for each thread" but
mostly we work single-threaded.  The good thing may be it could
be useful in debug mode to not suddenly pop out to a parent
member (yes, Joel!) - you'd move to the "throw" statement and be
able to examine your locals. But then your code would be
"littered with try/catch/throw