From 43a8af1da2247793082a37b111202a8a106f0071 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Johannes=20Schl=C3=BCter?= Date: Tue, 27 Oct 2009 14:42:50 +0000 Subject: [PATCH] Some more minor tweaks git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@289989 c90b9560-bf6c-de11-be94-00142212c4b1 --- internals2/memory/management.xml | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/internals2/memory/management.xml b/internals2/memory/management.xml index 7b8fcf286f..70732cdec3 100644 --- a/internals2/memory/management.xml +++ b/internals2/memory/management.xml @@ -116,11 +116,11 @@ As said above it is an essential part of the memory management to avoid - having memory leaks and therefore free all memory you've allocated. As a - safety net the Zend Engine will free all memory, which had been allocated - using above mentioned APIs at the end of a request. If PHP was built using - the --enable-debug configuration option this will lead to a - warning. + having memory leaks and therefore free all memory you've allocated as soon + as possible. As a safety net the Zend Engine will free all memory, which had + been allocated using above mentioned APIs at the end of a request. If PHP + was built using the --enable-debug configuration option this + will lead to a warning. @@ -143,7 +143,7 @@ ZEND_FUNCTION(leak) @@ -151,9 +151,9 @@ ZEND_FUNCTION(leak) - When dealing with PHP variables you have to make sure the variable is - allocated using emalloc and take care of the reference count. Details can - be found in . + When dealing with PHP variables you have to make sure the variable's + memory is allocated using emalloc and take care of the reference count. + Details can be found in .