Mercurial > cpython-lru_cache-weakref

diff Doc/api/refcounts.dat @ 15614:7bb7b72fa666 legacy-trunk

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Document Pyerr_Warn(). Add an XXX comment at the beginning expressing disappointment over the confusing way refcount behavior of arguments is documented.
author Guido van Rossum <guido@python.org>
date Tue, 19 Dec 2000 03:53:57 +0000
parents 7e514f1fe31f
children 0789dd062d6c
line wrap: on
line diff
--- a/Doc/api/refcounts.dat	Tue Dec 19 03:53:01 2000 +0000
+++ b/Doc/api/refcounts.dat	Tue Dec 19 03:53:57 2000 +0000
@@ -21,6 +21,13 @@
 # always return NULL.  This is used by some of the PyErr_*() functions, in
 # particular.
 
+# XXX NOTE: the 0/+1/-1 refcount information for arguments is
+# confusing!  Much more useful would be to indicate whether the
+# function "steals" a reference to the argument or not.  Take for
+# example PyList_SetItem(list, i, item).  This lists as a 0 change for
+# both the list and the item arguments.  However, in fact it steals a
+# reference to the item argument!
+
 # The parameter names are as they appear in the API manual, not the source
 # code. 
 
@@ -199,6 +206,10 @@
 PyErr_Format:char*:format::
 PyErr_Format::...::
 
+PyErr_Warn:int:::
+PyErr_Warn:PyObject*:category:0 or +1:
+PyErr_Warn:char*:message::
+
 PyEval_AcquireLock:void:::
 
 PyEval_AcquireThread:void:::