summaryrefslogtreecommitdiffstats
path: root/Doc/ext
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1997-07-17 15:58:43 (GMT)
committerGuido van Rossum <guido@python.org>1997-07-17 15:58:43 (GMT)
commitdebf2e8a5378a5eb5783297b0027331398f450e9 (patch)
tree0f360eab4042e6af51c46132abfc4d12681353cf /Doc/ext
parentc3fb88be8b5ae8953a35a23c22134f16931361ce (diff)
downloadcpython-debf2e8a5378a5eb5783297b0027331398f450e9.zip
cpython-debf2e8a5378a5eb5783297b0027331398f450e9.tar.gz
cpython-debf2e8a5378a5eb5783297b0027331398f450e9.tar.bz2
Fix dropped word.
Diffstat (limited to 'Doc/ext')
-rw-r--r--Doc/ext/ext.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/ext/ext.tex b/Doc/ext/ext.tex
index b32702e..d168aa6 100644
--- a/Doc/ext/ext.tex
+++ b/Doc/ext/ext.tex
@@ -879,7 +879,7 @@ program terminates. This is called a \dfn{memory leak}. On the other
hand, if a program calls \code{free()} for a block and then continues
to use the block, it creates a conflict with re-use of the block
through another \code{malloc()} call. This is called \dfn{using freed
-memory} has the same bad consequences as referencing uninitialized
+memory}. It has the same bad consequences as referencing uninitialized
data --- core dumps, wrong results, mysterious crashes.
Common causes of memory leaks are unusual paths through the code. For