Mercurial > cpython-lru_cache-weakref
diff Doc/lib/libthreading.tex @ 18416:33b4357aebb8 legacy-trunk
Fix up a few style nits -- avoid "e.g." and "i.e." -- these make
translation more difficult, as well as reading the English more
difficult for non-native speakers.
| author | Fred Drake <fdrake@acm.org> |
|---|---|
| date | Fri, 06 Jul 2001 20:30:11 +0000 |
| parents | 50e3380b086a |
| children | be5be989caff |
line wrap: on
line diff
--- a/Doc/lib/libthreading.tex Fri Jul 06 20:27:29 2001 +0000 +++ b/Doc/lib/libthreading.tex Fri Jul 06 20:30:11 2001 +0000 @@ -150,10 +150,11 @@ To lock the lock, a thread calls its \method{acquire()} method; this returns once the thread owns the lock. To unlock the lock, a -thread calls its \method{release()} method. \method{acquire()}/\method{release()} call pairs -may be nested; only the final \method{release()} (i.e. the \method{release()} of the -outermost pair) resets the lock to unlocked and allows another -thread blocked in \method{acquire()} to proceed. +thread calls its \method{release()} method. +\method{acquire()}/\method{release()} call pairs may be nested; only +the final \method{release()} (the \method{release()} of the outermost +pair) resets the lock to unlocked and allows another thread blocked in +\method{acquire()} to proceed. \begin{methoddesc}{acquire}{\optional{blocking\code{ = 1}}} Acquire a lock, blocking or non-blocking. @@ -453,7 +454,7 @@ There is the possibility that ``dummy thread objects'' are created. These are thread objects corresponding to ``alien threads''. These are threads of control started outside the -threading module, e.g. directly from C code. Dummy thread objects +threading module, such as directly from C code. Dummy thread objects have limited functionality; they are always considered alive, active, and daemonic, and cannot be \method{join()}ed. They are never deleted, since it is impossible to detect the termination of alien