Mercurial > cpython-lru_cache-weakref
diff Doc/api/api.tex @ 8029:95142c8a09c8 legacy-trunk
Typo: (and often severly limited) -- severely
Typo: (but not to the tuple or list into which the item it put!) -- is put
Thanks, AMK!
| author | Fred Drake <fdrake@acm.org> |
|---|---|
| date | Mon, 13 Apr 1998 00:53:42 +0000 |
| parents | 3b91affa333e |
| children | 5aacdd097941 |
line wrap: on
line diff
--- a/Doc/api/api.tex Mon Apr 13 00:50:04 1998 +0000 +++ b/Doc/api/api.tex Mon Apr 13 00:53:42 1998 +0000 @@ -115,7 +115,7 @@ \label{refcounts} The reference count is important because today's computers have a -finite (and often severly limited) memory size; it counts how many +finite (and often severely limited) memory size; it counts how many different places there are that have a reference to an object. Such a place could be another object, or a global (or static) \C{} variable, or a local variable in some \C{} function. When an object's reference count @@ -192,7 +192,7 @@ references; the two notable exceptions are \cfunction{PyList_SetItem()} and \cfunction{PyTuple_SetItem()}, which steal a reference to the item (but not to the tuple or list into which -the item it put!). These functions were designed to steal a reference +the item is put!). These functions were designed to steal a reference because of a common idiom for populating a tuple or list with newly created objects; for example, the code to create the tuple \code{(1, 2, "three")} could look like this (forgetting about error handling for
