From ffe58ca6ef2ec88afd2a345fa3100b34ad12737e Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Fri, 29 Sep 2000 17:31:54 +0000 Subject: [PATCH] Reversely --> Conversely This closes SourceForge bug #115673. --- Doc/api/api.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/api/api.tex b/Doc/api/api.tex index 18753c17afc..53ca462399a 100644 --- a/Doc/api/api.tex +++ b/Doc/api/api.tex @@ -4186,8 +4186,8 @@ current thread state. When releasing the lock and saving the thread state, the current thread state pointer must be retrieved before the lock is released (since another thread could immediately acquire the lock and store its own thread state in the global variable). -Reversely, when acquiring the lock and restoring the thread state, the -lock must be acquired before storing the thread state pointer. +Conversely, when acquiring the lock and restoring the thread state, +the lock must be acquired before storing the thread state pointer. Why am I going on with so much detail about this? Because when threads are created from C, they don't have the global interpreter