diff options
| author | MenTaLguY <mental@rydia.net> | 2006-04-29 17:30:08 +0000 |
|---|---|---|
| committer | mental <mental@users.sourceforge.net> | 2006-04-29 17:30:08 +0000 |
| commit | f689290c206611404fa1d8c8085d59c8b4ccfe3e (patch) | |
| tree | d686b09372e08b07ef7e37ce09a7546122a22dc9 | |
| parent | simplify wording (diff) | |
| download | inkscape-f689290c206611404fa1d8c8085d59c8b4ccfe3e.tar.gz inkscape-f689290c206611404fa1d8c8085d59c8b4ccfe3e.zip | |
emphasis
(bzr r621)
| -rw-r--r-- | doc/refcounting.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/refcounting.txt b/doc/refcounting.txt index bb8cc5d51..5dab790a0 100644 --- a/doc/refcounting.txt +++ b/doc/refcounting.txt @@ -108,7 +108,7 @@ free it now". For GC::Anchored objects, refcounting is merely an override 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 |