Remove now-obsolete staticforward/statichere discussion.

freddrake · freddrake · commit a3cd9bbaa3ee · 2002-07-17T16:40:39.000Z
diff --git a/Doc/ext/newtypes.tex b/Doc/ext/newtypes.tex
@@ -38,19 +38,14 @@ \section{The Basics
 The first bit that will be new is:
 
 \begin{verbatim}
-staticforward PyTypeObject noddy_NoddyType;
+static PyTypeObject noddy_NoddyType;
 \end{verbatim}
 
 This names the type object that will be defining further down in the
 file.  It can't be defined here because its definition has to refer to
 functions that have no yet been defined, but we need to be able to
 refer to it, hence the declaration.
 
-The \code{staticforward} is required to placate various brain dead
-compilers.  The actual definition of the object declared using
-\code{staticforward} should use \code{statichere} instead of
-\keyword{static}.
-
 \begin{verbatim}
 typedef struct {
     PyObject_HEAD
@@ -156,7 +151,7 @@ \section{The Basics
 Moving on, we come to the crunch --- the type object.
 
 \begin{verbatim}
-statichere PyTypeObject noddy_NoddyType = {
+static PyTypeObject noddy_NoddyType = {
     PyObject_HEAD_INIT(NULL)
     0,                          /* ob_size */
     "Noddy",                    /* tp_name */
@@ -175,9 +170,6 @@ \section{The Basics
 };
 \end{verbatim}
 
-(Note the use of \code{statichere} instead of \keyword{static}, since
-we used \code{staticforward} in the declaration.)
-
 Now if you go and look up the definition of \ctype{PyTypeObject} in
 \file{object.h} you'll see that it has many, many more fields that the
 definition above.  The remaining fields will be filled with zeros by
