[Python-checkins] CVS: python/dist/src/Doc/ext ext.tex,1.68.2.8,1.68.2.9

[Fred L. Drake]

Update of /projects/cvsroot/python/dist/src/Doc/ext
In directory weyr:/home/fdrake/projects/python/Doc-152p2/ext

Modified Files:
      Tag: release152p1-patches
	ext.tex 
Log Message:

A few minor improvements, but not all that's really needed.


Index: ext.tex
===================================================================
RCS file: /projects/cvsroot/python/dist/src/Doc/ext/ext.tex,v
retrieving revision 1.68.2.8
retrieving revision 1.68.2.9
diff -C2 -r1.68.2.8 -r1.68.2.9
*** ext.tex	2000/03/08 16:56:07	1.68.2.8
--- ext.tex	2000/03/21 19:29:01	1.68.2.9
***************
*** 45,49 ****
  
  This document assumes basic knowledge about Python.  For an informal
! introduction to the language, see the Python Tutorial.  The \emph{Python
  Reference Manual} gives a more formal definition of the language.  The
  \emph{Python Library Reference} documents the existing object types,
--- 45,49 ----
  
  This document assumes basic knowledge about Python.  For an informal
! introduction to the language, see the \emph{Python Tutorial}.  The \emph{Python
  Reference Manual} gives a more formal definition of the language.  The
  \emph{Python Library Reference} documents the existing object types,
***************
*** 75,79 ****
  
  The compilation of an extension module depends on its intended use as
! well as on your system setup; details are given in a later section.
  
  
--- 75,79 ----
  
  The compilation of an extension module depends on its intended use as
! well as on your system setup; details are given in later chapters.
  
  
***************
*** 95,99 ****
  \end{verbatim}
  
! Begin by creating a file \file{spammodule.c}.  (In general, if a
  module is called \samp{spam}, the C file containing its implementation
  is called \file{spammodule.c}; if the module name is very long, like
--- 95,99 ----
  \end{verbatim}
  
! Begin by creating a file \file{spammodule.c}.  (Historically, if a
  module is called \samp{spam}, the C file containing its implementation
  is called \file{spammodule.c}; if the module name is very long, like
***************
*** 103,107 ****
  
  \begin{verbatim}
! #include "Python.h"
  \end{verbatim}
  
--- 103,107 ----
  
  \begin{verbatim}
! #include <Python.h>
  \end{verbatim}
  
***************
*** 1629,1633 ****
  A module description line includes a module name, source files,
  options, variable references, and other input files, such
! as libraries or object files.  Consider a simple example::
  
  \begin{verbatim}
--- 1629,1633 ----
  A module description line includes a module name, source files,
  options, variable references, and other input files, such
! as libraries or object files.  Consider a simple example:
  
  \begin{verbatim}
***************
*** 1804,1808 ****
  
  Create a \file{Setup} file for your extension module, as described in
! Chapter \ref{building-on-unix}.
  
  Get David Ascher's \file{compile.py} script from
--- 1804,1808 ----
  
  Create a \file{Setup} file for your extension module, as described in
! chapter \ref{building-on-unix}.
  
  Get David Ascher's \file{compile.py} script from
***************
*** 1810,1814 ****
  create Microsoft Visual \Cpp{} project files.
  
! Open the DSW file in V\Cpp{} and select \strong{Build}.
  
  If your module creates a new type, you may have trouble with this line:
--- 1810,1814 ----
  create Microsoft Visual \Cpp{} project files.
  
! Open the DSW file in Visual \Cpp{} and select \strong{Build}.
  
  If your module creates a new type, you may have trouble with this line:
***************
*** 1844,1848 ****
  dynamically loaded, be aware of how your system works.
  
! In \UNIX{}, a shared object (.so) file contains code to be used by the
  program, and also the names of functions and data that it expects to
  find in the program.  When the file is joined to the program, all
--- 1844,1848 ----
  dynamically loaded, be aware of how your system works.
  
! In \UNIX{}, a shared object (\file{.so}) file contains code to be used by the
  program, and also the names of functions and data that it expects to
  find in the program.  When the file is joined to the program, all