summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>1998-02-16 14:47:27 (GMT)
committerFred Drake <fdrake@acm.org>1998-02-16 14:47:27 (GMT)
commit1aedbd8b0aabdb2a68748df4d1f10e2577e8d027 (patch)
tree0da6a6abfcbb0930e5a2dc29ec5f042744cc29ee
parent4de05a90beb7a9266093d2cd00e9dcb7f2705aa0 (diff)
downloadcpython-1aedbd8b0aabdb2a68748df4d1f10e2577e8d027.zip
cpython-1aedbd8b0aabdb2a68748df4d1f10e2577e8d027.tar.gz
cpython-1aedbd8b0aabdb2a68748df4d1f10e2577e8d027.tar.bz2
"--" --> "---" in two places.
-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 0045191..348f75a 100644
--- a/Doc/ext.tex
+++ b/Doc/ext.tex
@@ -140,7 +140,7 @@ doesn't have to understand two different types of \C{} functions.)
The \var{args} argument will be a pointer to a Python tuple object
containing the arguments. Each item of the tuple corresponds to an
argument in the call's argument list. The arguments are Python
-objects -- in order to do anything with them in our \C{} function we have
+objects --- in order to do anything with them in our \C{} function we have
to convert them to \C{} values. The function \code{PyArg_ParseTuple()}
in the Python API checks the argument types and converts them to \C{}
values. It uses a template string to determine the required types of
@@ -666,7 +666,7 @@ be nested.
\end{description}
It is possible to pass Python long integers where integers are
-requested; however no proper range checking is done -- the most
+requested; however no proper range checking is done --- the most
significant bits are silently truncated when the receiving field is
too small to receive the value (actually, the semantics are inherited
from downcasts in \C{} --- your milage may vary).
diff --git a/Doc/ext/ext.tex b/Doc/ext/ext.tex
index 0045191..348f75a 100644
--- a/Doc/ext/ext.tex
+++ b/Doc/ext/ext.tex
@@ -140,7 +140,7 @@ doesn't have to understand two different types of \C{} functions.)
The \var{args} argument will be a pointer to a Python tuple object
containing the arguments. Each item of the tuple corresponds to an
argument in the call's argument list. The arguments are Python
-objects -- in order to do anything with them in our \C{} function we have
+objects --- in order to do anything with them in our \C{} function we have
to convert them to \C{} values. The function \code{PyArg_ParseTuple()}
in the Python API checks the argument types and converts them to \C{}
values. It uses a template string to determine the required types of
@@ -666,7 +666,7 @@ be nested.
\end{description}
It is possible to pass Python long integers where integers are
-requested; however no proper range checking is done -- the most
+requested; however no proper range checking is done --- the most
significant bits are silently truncated when the receiving field is
too small to receive the value (actually, the semantics are inherited
from downcasts in \C{} --- your milage may vary).