traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Reversely --> Conversely 

This closes SourceForge bug #115673.
This commit is contained in:
Fred Drake 2000-09-29 17:31:54 +00:00
parent 45888ffbd4
commit ffe58ca6ef
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Doc/api/api.tex
View File

@ -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 state, the current thread state pointer must be retrieved before the
lock is released (since another thread could immediately acquire the lock is released (since another thread could immediately acquire the
lock and store its own thread state in the global variable). lock and store its own thread state in the global variable).
Reversely, when acquiring the lock and restoring the thread state, the Conversely, when acquiring the lock and restoring the thread state,
lock must be acquired before storing the thread state pointer. the lock must be acquired before storing the thread state pointer.
Why am I going on with so much detail about this? Because when 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 threads are created from C, they don't have the global interpreter