summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1996-12-13 02:38:17 (GMT)
committerGuido van Rossum <guido@python.org>1996-12-13 02:38:17 (GMT)
commitd16ddb610a8f09883303ee87c1609bf3bd8a40a8 (patch)
tree919310944f34f855578ba8c20f3feea98467289e /Doc
parentf630f6b93deeca767404d936c548c16c9fb8d561 (diff)
downloadcpython-d16ddb610a8f09883303ee87c1609bf3bd8a40a8.zip
cpython-d16ddb610a8f09883303ee87c1609bf3bd8a40a8.tar.gz
cpython-d16ddb610a8f09883303ee87c1609bf3bd8a40a8.tar.bz2
Typos reported by Tamito Kajiyama.
Diffstat (limited to 'Doc')
-rw-r--r--Doc/ext.tex4
-rw-r--r--Doc/ext/ext.tex4
2 files changed, 4 insertions, 4 deletions
diff --git a/Doc/ext.tex b/Doc/ext.tex
index f133a3f..83d1078 100644
--- a/Doc/ext.tex
+++ b/Doc/ext.tex
@@ -196,7 +196,7 @@ or \code{NULL} if no exception has occurred. You normally don't need
to call \code{PyErr_Occurred()} to see whether an error occurred in a
function call, since you should be able to tell from the return value.
-When a function \var{f} that calls another function var{g} detects
+When a function \var{f} that calls another function \var{g} detects
that the latter fails, \var{f} should itself return an error value
(e.g. \code{NULL} or \code{-1}). It should \emph{not} call one of the
\code{PyErr_*()} functions --- one has already been called by \var{g}.
@@ -305,7 +305,7 @@ passing it the string we just got from \code{PyArg_ParseTuple()}:
sts = system(command);
\end{verbatim}
-Our \code{spam.system()} function must return the value of \code{sys}
+Our \code{spam.system()} function must return the value of \code{sts}
as a Python object. This is done using the function
\code{Py_BuildValue()}, which is something like the inverse of
\code{PyArg_ParseTuple()}: it takes a format string and an arbitrary
diff --git a/Doc/ext/ext.tex b/Doc/ext/ext.tex
index f133a3f..83d1078 100644
--- a/Doc/ext/ext.tex
+++ b/Doc/ext/ext.tex
@@ -196,7 +196,7 @@ or \code{NULL} if no exception has occurred. You normally don't need
to call \code{PyErr_Occurred()} to see whether an error occurred in a
function call, since you should be able to tell from the return value.
-When a function \var{f} that calls another function var{g} detects
+When a function \var{f} that calls another function \var{g} detects
that the latter fails, \var{f} should itself return an error value
(e.g. \code{NULL} or \code{-1}). It should \emph{not} call one of the
\code{PyErr_*()} functions --- one has already been called by \var{g}.
@@ -305,7 +305,7 @@ passing it the string we just got from \code{PyArg_ParseTuple()}:
sts = system(command);
\end{verbatim}
-Our \code{spam.system()} function must return the value of \code{sys}
+Our \code{spam.system()} function must return the value of \code{sts}
as a Python object. This is done using the function
\code{Py_BuildValue()}, which is something like the inverse of
\code{PyArg_ParseTuple()}: it takes a format string and an arbitrary