There are few concerns: 1) It is likely that the exception is non recoverable, from the place it occurred and may need to be wound back multiple levels 2) Runt

There are few concerns: 1) It is likely that the exception is non recoverable, from the place it occurred and may need to be wound back multiple levels 2) Runtime that defensively handle exceptions as specified at every point will need to keep stack state indefinitely deep I believe, rather than exception syntax, the issue is abuse of exceptions. Exceptions must be raised on recoverable errors, but they must be handled at the right abstraction level. So how about raising the 'throws' on your functions and then handle them at the right abstraction level. Why not spent a little time designing your exception handling tree before implementing. That said, the 'recover' keyword may be really helpful in many cases.