Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Diff of /Doc/api/newtypes.tex [8d4b25] .. [7b66cd] Maximize Restore

  Switch to side-by-side view

--- a/Doc/api/newtypes.tex
+++ b/Doc/api/newtypes.tex
@@ -226,7 +226,7 @@
 
 \begin{datadesc}{METH_VARARGS}
   This is the typical calling convention, where the methods have the
-  type \ctype{PyMethodDef}. The function expects two
+  type \ctype{PyCFunction}. The function expects two
   \ctype{PyObject*} values.  The first one is the \var{self} object for
   methods; for module functions, it has the value given to
   \cfunction{Py_InitModule4()} (or \NULL{} if
@@ -1151,7 +1151,7 @@
   The function signature is
 
 \begin{verbatim}
-tp_init(PyObject *self, PyObject *args, PyObject *kwds)
+int tp_init(PyObject *self, PyObject *args, PyObject *kwds)
 \end{verbatim}
 
   The self argument is the instance to be initialized; the \var{args}
@@ -1179,7 +1179,7 @@
   The function signature is
 
 \begin{verbatim}
-tp_alloc(PyTypeObject *self, int nitems)
+PyObject *tp_alloc(PyTypeObject *self, int nitems)
 \end{verbatim}
 
   The purpose of this function is to separate memory allocation from
@@ -1215,7 +1215,7 @@
   The function signature is
 
 \begin{verbatim}
-tp_new(PyTypeObject *subtype, PyObject *args, PyObject *kwds)
+PyObject *tp_new(PyTypeObject *subtype, PyObject *args, PyObject *kwds)
 \end{verbatim}
 
   The subtype argument is the type of the object being created; the