[Python-checkins] python/dist/src/Doc/ext newtypes.tex,1.16,1.17

[fdrake@users.sourceforge.net]

Update of /cvsroot/python/python/dist/src/Doc/ext
In directory usw-pr-cvs1:/tmp/cvs-serv21191

Modified Files:
	newtypes.tex 
Log Message:
Remove now-obsolete staticforward/statichere discussion.

Index: newtypes.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/ext/newtypes.tex,v
retrieving revision 1.16
retrieving revision 1.17
diff -C2 -d -r1.16 -r1.17
*** newtypes.tex	14 May 2002 22:02:07 -0000	1.16
--- newtypes.tex	17 Jul 2002 16:40:39 -0000	1.17
***************
*** 39,43 ****
  
  \begin{verbatim}
! staticforward PyTypeObject noddy_NoddyType;
  \end{verbatim}
  
--- 39,43 ----
  
  \begin{verbatim}
! static PyTypeObject noddy_NoddyType;
  \end{verbatim}
  
***************
*** 47,55 ****
  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 {
--- 47,50 ----
***************
*** 157,161 ****
  
  \begin{verbatim}
! statichere PyTypeObject noddy_NoddyType = {
      PyObject_HEAD_INIT(NULL)
      0,                          /* ob_size */
--- 152,156 ----
  
  \begin{verbatim}
! static PyTypeObject noddy_NoddyType = {
      PyObject_HEAD_INIT(NULL)
      0,                          /* ob_size */
***************
*** 175,181 ****
  };
  \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
--- 170,173 ----