diff options
| author | Fred Drake <fdrake@acm.org> | 2000-09-29 17:31:54 (GMT) |
|---|---|---|
| committer | Fred Drake <fdrake@acm.org> | 2000-09-29 17:31:54 (GMT) |
| commit | ffe58ca6ef2ec88afd2a345fa3100b34ad12737e (patch) | |
| tree | 25722221fd8235056fb1bfcc339298d332ef612f /Doc/api/api.tex | |
| parent | 45888ffbd446bb689384f14ec994d712e8751e1c (diff) | |
| download | cpython-ffe58ca6ef2ec88afd2a345fa3100b34ad12737e.zip cpython-ffe58ca6ef2ec88afd2a345fa3100b34ad12737e.tar.gz cpython-ffe58ca6ef2ec88afd2a345fa3100b34ad12737e.tar.bz2 | |
Reversely --> Conversely
This closes SourceForge bug #115673.
Diffstat (limited to 'Doc/api/api.tex')
| -rw-r--r-- | Doc/api/api.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/api/api.tex b/Doc/api/api.tex index 18753c1..53ca462 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 |