From b56ad422f70d8be84a1c3414fff85f27d42e99c5 Mon Sep 17 00:00:00 2001 From: "Frank B. Brokken" Date: Thu, 28 Nov 2013 08:19:38 +0100 Subject: [PATCH] typo repaired --- annotations/yo/stl/events.yo | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/annotations/yo/stl/events.yo b/annotations/yo/stl/events.yo index 155c8910..b5974bee 100644 --- a/annotations/yo/stl/events.yo +++ b/annotations/yo/stl/events.yo @@ -57,7 +57,7 @@ Condition variables come in two flavors: objects of the class with objects of type tt(unique_lock). This combination allows optimizations resulting in an increased efficiency compared to the efficiency that can be obtained with objects of the class - hi(condition_variable_any)tt(stdLLcondition_variable_any) that can be used + hi(condition_variable_any)tt(std::condition_variable_any) that can be used with any (e.g., user-supplied) lock types. The condition variable classes offer members like tt(wait, wait_for,