Remove now-obsolete staticforward/statichere discussion.
diff --git a/Doc/ext/newtypes.tex b/Doc/ext/newtypes.tex
index 12e728b..4763d18 100644
--- a/Doc/ext/newtypes.tex
+++ b/Doc/ext/newtypes.tex
@@ -38,7 +38,7 @@
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
@@ -46,11 +46,6 @@
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 @@
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 @@
};
\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