diff options
| author | Tim Peters <tim.peters@gmail.com> | 2001-12-07 17:51:41 (GMT) |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2001-12-07 17:51:41 (GMT) |
| commit | 874c4f0f998ceae0e643906b6c742b9748ed4055 (patch) | |
| tree | a15645d597183d9ed755480a9667fdd83b2ff9f9 | |
| parent | 024e647972671cdced6fc3487740ca8580860416 (diff) | |
| download | cpython-874c4f0f998ceae0e643906b6c742b9748ed4055.zip cpython-874c4f0f998ceae0e643906b6c742b9748ed4055.tar.gz cpython-874c4f0f998ceae0e643906b6c742b9748ed4055.tar.bz2 | |
Trivial spelling repair on new cyclic garbage text.
| -rw-r--r-- | Doc/ext/extending.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/ext/extending.tex b/Doc/ext/extending.tex index 7fe07b8..a0a0440 100644 --- a/Doc/ext/extending.tex +++ b/Doc/ext/extending.tex @@ -1238,9 +1238,9 @@ cycles. This allows applications to not worry about creating direct or indirect circular references; these are the weakness of garbage collection implemented using only reference counting. Reference cycles consist of objects which contain (possibly indirect) references -themselves so that each object in the cycle has a reference count +to themselves, so that each object in the cycle has a reference count which is non-zero. Typical reference counting implementations are not -able to reclaim the memory beloning to any objects in a reference +able to reclaim the memory belonging to any objects in a reference cycle, or referenced from the objects in the cycle, even though there are no further references to the cycle itself. |