From afbce41644ccfe8c46c12911afdffcfa1a733bc0 Mon Sep 17 00:00:00 2001 From: Steve MacLean Date: Mon, 4 Mar 2019 20:29:11 -0500 Subject: [PATCH] Remove BEGIN/END_EXCEPTION_GLUE from botr Commit migrated from https://github.com/dotnet/coreclr/commit/77fcaf6b738941a0c5dc3c00b70b49c7d9f63b69 --- docs/coreclr/botr/exceptions.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/coreclr/botr/exceptions.md b/docs/coreclr/botr/exceptions.md index 5e8a62c..5f0e877 100644 --- a/docs/coreclr/botr/exceptions.md +++ b/docs/coreclr/botr/exceptions.md @@ -301,5 +301,3 @@ Miscellaneous ============= There are actually a lot of macros involved in EX_TRY. Most of them should never, ever, be used outside of the macro implementations. - -One set, BEGIN_EXCEPTION_GLUE / END_EXCEPTION_GLUE, deserves special mention. These were intended to be transitional macros, and were to be replaced with more appropriate macros in the Whidbey project. Of course, they worked just fine, and so they weren't all replaced. Ideally, all instances will be converted during a "cleanup" milestone, and the macros removed. In the meantime, any CLR dev tempted to use them should resist, and instead write EX_TRY/EX_CATCH/EX_CATCH_END or EX_CATCH_HRESULT. -- 2.7.4