diff options
| author | Michael W. Hudson <mwh@python.net> | 2003-11-07 11:45:34 (GMT) |
|---|---|---|
| committer | Michael W. Hudson <mwh@python.net> | 2003-11-07 11:45:34 (GMT) |
| commit | ff1f1949820126cce5c17f15c37843ccfd100564 (patch) | |
| tree | 52d23e1900c1ef3eba0b9e867881f28efa03d7bf | |
| parent | dc62aeca4cd13ead75adece6a99089457087e687 (diff) | |
| download | cpython-ff1f1949820126cce5c17f15c37843ccfd100564.zip cpython-ff1f1949820126cce5c17f15c37843ccfd100564.tar.gz cpython-ff1f1949820126cce5c17f15c37843ccfd100564.tar.bz2 | |
Fix the problem addressed by patch
[ 819012 ] Fix for former/latter confusion in Extending documentation
although not by using supplied patch.
| -rw-r--r-- | Doc/ext/extending.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/ext/extending.tex b/Doc/ext/extending.tex index bfd6b04..95e4546 100644 --- a/Doc/ext/extending.tex +++ b/Doc/ext/extending.tex @@ -819,7 +819,7 @@ dynamic allocation and deallocation of memory on the heap. In C, this is done using the functions \cfunction{malloc()} and \cfunction{free()}. In \Cpp, the operators \keyword{new} and \keyword{delete} are used with essentially the same meaning and -we'll restrict the following discussion to the latter. +we'll restrict the following discussion to the C case. Every block of memory allocated with \cfunction{malloc()} should eventually be returned to the pool of available memory by exactly one |