summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: fa0d3e8)
raw | patch | inline | side by side (parent: fa0d3e8)
author | mental <mental@users.sourceforge.net> | |
Sat, 29 Apr 2006 17:30:08 +0000 (17:30 +0000) | ||
committer | mental <mental@users.sourceforge.net> | |
Sat, 29 Apr 2006 17:30:08 +0000 (17:30 +0000) |
doc/refcounting.txt | patch | blob | history |
diff --git a/doc/refcounting.txt b/doc/refcounting.txt
index bb8cc5d5183ca077e05d254bcf83fa8c2b0102c0..5dab790a059a20aa308c961012bbda54038c8391 100644 (file)
--- a/doc/refcounting.txt
+++ b/doc/refcounting.txt
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