...> where you want to identify code that runs only if an exception is not raised. Independently, Erlang introduced the same thing: try Expr of Pattern1 [when Guard1] -> Body1; ... catch ExceptionPattern1 [when ExceptionGuard1] -> ExceptionBody1 ... after FinalBody I have known this idiom as ...

...pdf where you want to identify code that runs only if an exception is not raised. Independently, Erlang introduced the same thing: try Expr of Pattern1 [when Guard1] -> Body1; ... catch ExceptionPattern1 [when ExceptionGuard1] -> ExceptionBody1 ... after FinalBody I have known this idiom as try-catch-finally (I ...

....pdf where you want to identify code that runs only if an exception is not raised. Independently, Erlang introduced the same thing: try Expr of Pattern1 [when Guard1] -> Body1; ... catch ExceptionPattern1 [when ExceptionGuard1] -> ExceptionBody1 ... after FinalBody I have known this idiom as try-catch-finally (I think these keywords are...

.../sml/ExceptionalSyntax.pdf where you want to identify code that runs only if an exception is not raised. Independently, Erlang introduced the same thing: try Expr of Pattern1 [when Guard1] -> Body1; ... catch ExceptionPattern1 [when ExceptionGuard1] -> ExceptionBody1 ... after FinalBody The point is that the handler is wrapped only around Expr, not Body1, ...