[Python-checkins] CVS: python/dist/src/Doc/tut tut.tex,1.151,1.152

[Fred L. Drake]

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

Modified Files:
	tut.tex 
Log Message:
Clean up some markup cruft.  A number of the macros that take no
parameters (like \UNIX) are commonly entered using an empty group to
separate the markup from a following inter-word space; this is not
needed when the next character is punctuation, or the markup is the
last thing in the enclosing group.  These cases were marked
inconsistently; the empty group is now *only* used when needed.


Index: tut.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/tut/tut.tex,v
retrieving revision 1.151
retrieving revision 1.152
diff -C2 -d -r1.151 -r1.152
*** tut.tex	2001/10/16 03:25:00	1.151
--- tut.tex	2001/11/28 07:26:15	1.152
***************
*** 53,57 ****
  \citetitle[../ref/ref.html]{Python Reference Manual} gives a more
  formal definition of the language.  To write extensions in C or
! \Cpp{}, read \citetitle[../ext/ext.html]{Extending and Embedding the
  Python Interpreter} and \citetitle[../api/api.html]{Python/C API
  Reference}.  There are also several books covering Python in depth.
--- 53,57 ----
  \citetitle[../ref/ref.html]{Python Reference Manual} gives a more
  formal definition of the language.  To write extensions in C or
! \Cpp, read \citetitle[../ext/ext.html]{Extending and Embedding the
  Python Interpreter} and \citetitle[../api/api.html]{Python/C API
  Reference}.  There are also several books covering Python in depth.
***************
*** 183,187 ****
  
  The interpreter's line-editing features usually aren't very
! sophisticated.  On \UNIX{}, whoever installed the interpreter may have
  enabled support for the GNU readline library, which adds more
  elaborate interactive editing and history features. Perhaps the
--- 183,187 ----
  
  The interpreter's line-editing features usually aren't very
! sophisticated.  On \UNIX, whoever installed the interpreter may have
  enabled support for the GNU readline library, which adds more
  elaborate interactive editing and history features. Perhaps the
***************
*** 2231,2235 ****
  directory names.  When \envvar{PYTHONPATH} is not set, or when the file
  is not found there, the search continues in an installation-dependent
! default path; on \UNIX{}, this is usually \file{.:/usr/local/lib/python}.
  
  Actually, modules are searched in the list of directories given by the 
--- 2231,2235 ----
  directory names.  When \envvar{PYTHONPATH} is not set, or when the file
  is not found there, the search continues in an installation-dependent
! default path; on \UNIX, this is usually \file{.:/usr/local/lib/python}.
  
  Actually, modules are searched in the list of directories given by the 
***************
*** 2600,2604 ****
  
  %(One could design a notation to refer to parent packages, similar to
! %the use of ".." to refer to the parent directory in Unix and Windows
  %filesystems.  In fact, the \module{ni} module, which was the
  %ancestor of this package system, supported this using \code{__} for
--- 2600,2604 ----
  
  %(One could design a notation to refer to parent packages, similar to
! %the use of ".." to refer to the parent directory in \UNIX{} and Windows
  %filesystems.  In fact, the \module{ni} module, which was the
  %ancestor of this package system, supported this using \code{__} for
***************
*** 3336,3340 ****
  make occasional use of Smalltalk and \Cpp{} terms.  (I would use Modula-3
  terms, since its object-oriented semantics are closer to those of
! Python than \Cpp{}, but I expect that few readers have heard of it.)
  
  I also have to warn you that there's a terminological pitfall for
--- 3336,3340 ----
  make occasional use of Smalltalk and \Cpp{} terms.  (I would use Modula-3
  terms, since its object-oriented semantics are closer to those of
! Python than \Cpp, but I expect that few readers have heard of it.)
  
  I also have to warn you that there's a terminological pitfall for
***************
*** 3593,3597 ****
  The first I'll call \emph{data attributes}.  These correspond to
  ``instance variables'' in Smalltalk, and to ``data members'' in
! \Cpp{}.  Data attributes need not be declared; like local variables,
  they spring into existence when they are first assigned to.  For
  example, if \code{x} is the instance of \class{MyClass} created above,
--- 3593,3597 ----
  The first I'll call \emph{data attributes}.  These correspond to
  ``instance variables'' in Smalltalk, and to ``data members'' in
! \Cpp.  Data attributes need not be declared; like local variables,
  they spring into existence when they are first assigned to.  For
  example, if \code{x} is the instance of \class{MyClass} created above,