From 4044c53ebfa36d57c993f5ba37bd35c3c8912a7e Mon Sep 17 00:00:00 2001 From: Jakub Vrana Date: Fri, 20 Nov 2009 13:48:44 +0000 Subject: [PATCH] Fix build git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@291083 c90b9560-bf6c-de11-be94-00142212c4b1 --- features/gc.xml | 8 ++++---- reference/nis/configure.xml | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/features/gc.xml b/features/gc.xml index 77fd8c0b03..efad31292f 100644 --- a/features/gc.xml +++ b/features/gc.xml @@ -1,12 +1,12 @@ - + Garbage Collection This section explains the merits of the new Garbage Collection (also known as GC) mechanism that is part of PHP 5.3. This was originally written as a - three part column for php|architect. + three part column for php|architect. @@ -40,7 +40,7 @@ $a = "new string"; user-land reference has been created. The "refcount" is set to "1" as there is only one symbol that makes use of this variable container. Note that if "refcount" is "1", "is_ref" is always "false". If you have Xdebug installed, you can display this + xlink:href='&url.xdebug;'>Xdebug installed, you can display this information by calling: @@ -301,7 +301,7 @@ a: (refcount=2, is_ref=1)=array ( Traditionally, reference counting memory mechanisms, such as that used by PHP, fail to address those circular reference memory leaks. Back in 2007, while looking into this issue, I was pointed to a paper by David F. Bacon - and V.T. Rajan titled "Concurrent Cycle + and V.T. Rajan titled "Concurrent Cycle Collection in Reference Counted Systems". Although the paper was written with Java in mind, I started to play around with it to see if it was feasible to implement the synchronous algorithm, as outlined in the diff --git a/reference/nis/configure.xml b/reference/nis/configure.xml index b718c16c94..e3499ad553 100644 --- a/reference/nis/configure.xml +++ b/reference/nis/configure.xml @@ -1,6 +1,6 @@ -
+
&reftitle.install; &pecl.info;