From 7bb2f39db0c9a5dc61f97b395c4700080688f259 Mon Sep 17 00:00:00 2001 From: mental Date: Sat, 29 Apr 2006 18:42:29 +0000 Subject: [PATCH] clarify wording, and that these are rules of thumb --- doc/refcounting.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/refcounting.txt b/doc/refcounting.txt index a3cd02058..a27fb21fb 100644 --- a/doc/refcounting.txt +++ b/doc/refcounting.txt @@ -85,7 +85,7 @@ as it added and removed them. ANCHORED OBJECTS -The garbage collector can see pointers in: +As a rule of thumb, the garbage collector can see pointers in: * global/static variables in the program @@ -108,8 +108,8 @@ It cannot see pointers in: Since a lot of important objects (e.g. gtkmm widgets or Glib collections) fall into the latter category, I've provided the GC::Anchored class from which garbage-collector managed classes can be derived if they may be -remembered exclusively by such places. As noted earlier, the associated -ref and unref functions are GC::anchor() and GC::release(), respectively. +remembered in such places. As noted earlier, the associated ref and unref +functions are GC::anchor() and GC::release(), respectively. For most refcounted objects, a nonzero refcount means "this object is in use", and a zero refcount means "this object is no longer in use, you can -- 2.30.2