From cc7e33931673a5c5caffe0a8ab583aa2a88b85ac Mon Sep 17 00:00:00 2001 From: mental Date: Sat, 29 Apr 2006 17:26:23 +0000 Subject: [PATCH] minor verbage tweaking --- doc/refcounting.txt | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/refcounting.txt b/doc/refcounting.txt index b6a7bf433..6ba506e4d 100644 --- a/doc/refcounting.txt +++ b/doc/refcounting.txt @@ -9,10 +9,11 @@ which is supposed to reflect the number of outstanding references to it. 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 -- 2.39.5