summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 6853ce5)
raw | patch | inline | side by side (parent: 6853ce5)
author | mental <mental@users.sourceforge.net> | |
Sat, 29 Apr 2006 17:26:23 +0000 (17:26 +0000) | ||
committer | mental <mental@users.sourceforge.net> | |
Sat, 29 Apr 2006 17:26:23 +0000 (17:26 +0000) |
doc/refcounting.txt | patch | blob | history |
diff --git a/doc/refcounting.txt b/doc/refcounting.txt
index b6a7bf433e195015df0882299eaebedcc88516cf..6ba506e4d1f4fa7d51a292ffd1e64342fe5124f1 100644 (file)
--- a/doc/refcounting.txt
+++ b/doc/refcounting.txt
When that counter falls to zero, the object can be freed.
This releases the programmer from worrying about having freed an object
-while somebody else is still using it. Simply "ref" the object (increment
-the counter) when you first hold onto it, and "unref" it (decrement the
-counter) when you don't need it anymore. The ultimate decision to free
-the object is made for you behind the scenes.
+while somebody else is still using it (or someone else freeing while
+you're using it!). Simply "ref" the object (increment the counter) to
+stake your claim, and then "unref" it (decrement the counter) when you don't
+need it anymore. The ultimate decision to free the object is made safely
+behind the scenes.
You should "ref" an object whenever you plan to hold onto it while
transferring control to another part of the code (which might otherwise