summaryrefslogtreecommitdiffstats
path: root/doc/refcounting.txt
diff options
context:
space:
mode:
authorMenTaLguY <mental@rydia.net>2006-04-29 18:42:29 +0000
committermental <mental@users.sourceforge.net>2006-04-29 18:42:29 +0000
commit335205608ef28f2349fa3e2c5da74816a698fd12 (patch)
treeb6fb421cf6a92f04e0a5a7e5c5d25620ba9961fe /doc/refcounting.txt
parentgc visibility rules (diff)
downloadinkscape-335205608ef28f2349fa3e2c5da74816a698fd12.tar.gz
inkscape-335205608ef28f2349fa3e2c5da74816a698fd12.zip
clarify wording, and that these are rules of thumb
(bzr r625)
Diffstat (limited to 'doc/refcounting.txt')
-rw-r--r--doc/refcounting.txt6
1 files 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