From 273888e56c4605bcaa14b8717dc747a7b1f142f1 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Wed, 9 Apr 2003 18:17:18 +0000 Subject: Backport comments about PyObject_Type() (HEAD revisions 1.24, 1.25). --- Doc/api/abstract.tex | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/Doc/api/abstract.tex b/Doc/api/abstract.tex index 952b3d6..ee26a27 100644 --- a/Doc/api/abstract.tex +++ b/Doc/api/abstract.tex @@ -296,9 +296,13 @@ determination. \begin{cfuncdesc}{PyObject*}{PyObject_Type}{PyObject *o} When \var{o} is non-\NULL, returns a type object corresponding to the object type of object \var{o}. On failure, raises - \exception{SystemError} and returns \NULL. This is equivalent to - the Python expression \code{type(\var{o})}. - \bifuncindex{type} + \exception{SystemError} and returns \NULL.\bifuncindex{type} + This is equivalent to the Python expression \code{type(\var{o})}. + This function increments the reference count of the return value. + There's really no reason to use this function instead of the + common expression \code{\var{o}->ob_type}, which returns a pointer + of type \ctype{PyTypeObject*}, except when the incremented reference + count is needed. \end{cfuncdesc} \begin{cfuncdesc}{int}{PyObject_TypeCheck}{PyObject *o, PyTypeObject *type} -- cgit v0.12