mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-11-01 18:51:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 15

Fix dropped word.

Browse source
This commit is contained in:
Guido van Rossum 1997-07-17 15:58:43 +00:00
parent c3fb88be8b
commit debf2e8a53
2 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Doc/ext.tex
View file

@ -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 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 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 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. data --- core dumps, wrong results, mysterious crashes.
Common causes of memory leaks are unusual paths through the code. For Common causes of memory leaks are unusual paths through the code. For

2
Doc/ext/ext.tex
View file

@ -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 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 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 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. data --- core dumps, wrong results, mysterious crashes.
Common causes of memory leaks are unusual paths through the code. For Common causes of memory leaks are unusual paths through the code. For