From 47a031987f97e8b703beb57b6c6780da0adea0b9 Mon Sep 17 00:00:00 2001 From: Felipe Pessoto Date: Tue, 1 Mar 2016 21:17:37 -0300 Subject: [PATCH] Anchor Tag fix --- Documentation/botr/threading.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/botr/threading.md b/Documentation/botr/threading.md index 4eb8e34..2e13d52 100644 --- a/Documentation/botr/threading.md +++ b/Documentation/botr/threading.md @@ -173,7 +173,7 @@ The [Rules of the Code](../coding-guidelines/clr-code-guide.md) document describ Crst ---- -Just as Monitor is the preferred locking mechanism for managed code, Crst is the preferred mechanism for VM code. Like Monitor, Crst is a hybrid lock that is aware of hosts and GC modes. Crst also implements deadlock avoidance via "lock leveling," described in the [Crst Leveling chapter of the BotR](../coding-guidelines/clr-code-guide.md#entering-and-leaving-crsts). +Just as Monitor is the preferred locking mechanism for managed code, Crst is the preferred mechanism for VM code. Like Monitor, Crst is a hybrid lock that is aware of hosts and GC modes. Crst also implements deadlock avoidance via "lock leveling," described in the [Crst Leveling chapter of the BotR](../coding-guidelines/clr-code-guide.md#264-entering-and-leaving-crsts). It is generally illegal to acquire a Crst while in cooperative mode, though exceptions are made where absolutely necessary. -- 2.7.4