[Python-checkins] python/dist/src/Doc/ext extending.tex,1.19,1.20

[fdrake@sourceforge.net]

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

Modified Files:
	extending.tex 
Log Message:
Fix broken reference, minor clarification.

Index: extending.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/ext/extending.tex,v
retrieving revision 1.19
retrieving revision 1.20
diff -C2 -d -r1.19 -r1.20
*** extending.tex	12 Apr 2002 19:08:31 -0000	1.19
--- extending.tex	16 May 2002 13:48:14 -0000	1.20
***************
*** 415,430 ****
  There are two more things to do before you can use your new extension:
  compiling and linking it with the Python system.  If you use dynamic
! loading, the details depend on the style of dynamic loading your
! system uses; see the chapters about building extension modules on
! \UNIX{} (chapter \ref{building-on-unix}) and Windows (chapter
! \ref{building-on-windows}) for more information about this.
! % XXX Add information about MacOS  
  
  If you can't use dynamic loading, or if you want to make your module a
  permanent part of the Python interpreter, you will have to change the
  configuration setup and rebuild the interpreter.  Luckily, this is
! very simple: just place your file (\file{spammodule.c} for example) in
! the \file{Modules/} directory of an unpacked source distribution, add
! a line to the file \file{Modules/Setup.local} describing your file:
  
  \begin{verbatim}
--- 415,432 ----
  There are two more things to do before you can use your new extension:
  compiling and linking it with the Python system.  If you use dynamic
! loading, the details may depend on the style of dynamic loading your
! system uses; see the chapters about building extension modules
! (chapter \ref{building}) and additional information that pertains only
! to building on Windows (chapter \ref{building-on-windows}) for more
! information about this.
! % XXX Add information about Mac OS
  
  If you can't use dynamic loading, or if you want to make your module a
  permanent part of the Python interpreter, you will have to change the
  configuration setup and rebuild the interpreter.  Luckily, this is
! very simple on \UNIX: just place your file (\file{spammodule.c} for
! example) in the \file{Modules/} directory of an unpacked source
! distribution, add a line to the file \file{Modules/Setup.local}
! describing your file:
  
  \begin{verbatim}