[Python-checkins] python/dist/src/Doc/ext extending.tex,1.30,1.31

rhettinger at users.sourceforge.net rhettinger at users.sourceforge.net
Sat Jan 1 01:29:04 CET 2005

Update of /cvsroot/python/python/dist/src/Doc/ext
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3901/Doc/ext

Modified Files:
Log Message:
SF Patch #1093896:  miscellaneous doc typos

Index: extending.tex
RCS file: /cvsroot/python/python/dist/src/Doc/ext/extending.tex,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -d -r1.30 -r1.31
--- extending.tex	29 Jun 2004 03:48:23 -0000	1.30
+++ extending.tex	1 Jan 2005 00:28:30 -0000	1.31
@@ -23,7 +23,7 @@
 of Monty Python fans...) and let's say we want to create a Python
 interface to the C library function \cfunction{system()}.\footnote{An
 interface for this function already exists in the standard module
-\module{os} --- it was chosen as a simple and straightfoward example.}
+\module{os} --- it was chosen as a simple and straightforward example.}
 This function takes a null-terminated character string as argument and
 returns an integer.  We want this function to be callable from Python
 as follows:
@@ -1002,8 +1002,8 @@
 The object reference returned from a C function that is called from
-Python must be an owned reference --- ownership is tranferred from the
-function to its caller.
+Python must be an owned reference --- ownership is transferred from
+the function to its caller.
 \subsection{Thin Ice
@@ -1147,7 +1147,7 @@
 linked by the C compiler, global or static objects with constructors
 cannot be used.  This is not a problem if the main program is linked
 by the \Cpp{} compiler.  Functions that will be called by the
-Python interpreter (in particular, module initalization functions)
+Python interpreter (in particular, module initialization functions)
 have to be declared using \code{extern "C"}.
 It is unnecessary to enclose the Python header files in
 \code{extern "C" \{...\}} --- they use this form already if the symbol

More information about the Python-checkins mailing list