From 9f5d0a91cacc2665b7244e6b1d85028ba4908888 Mon Sep 17 00:00:00 2001 From: mental Date: Sat, 29 Apr 2006 17:30:08 +0000 Subject: [PATCH] emphasis --- doc/refcounting.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/refcounting.txt b/doc/refcounting.txt index bb8cc5d51..5dab790a0 100644 --- a/doc/refcounting.txt +++ b/doc/refcounting.txt @@ -108,7 +108,7 @@ free it now". For GC::Anchored objects, refcounting is merely an override to the normal operation of the garbage collector, so the rules are relaxed somewhat: a nonzero refcount merely means "the object is in use in places that the garbage collector can't see", and a zero refcount asserts that "the garbage -collector can see every use that matters". +collector can now see every use that matters". While GC::Anchored objects start with an initial refcount of one like any other refcounted type, in most cases it's safe (and convenient) to -- 2.30.2