From: mental Date: Sat, 29 Apr 2006 17:28:50 +0000 (+0000) Subject: simplify wording X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=fa0d3e877e4e340c200105e84432f4a6a375143a;p=inkscape.git simplify wording --- diff --git a/doc/refcounting.txt b/doc/refcounting.txt index 6ba506e4d..bb8cc5d51 100644 --- a/doc/refcounting.txt +++ b/doc/refcounting.txt @@ -32,7 +32,8 @@ from GC::Anchored -- more on that later). [ note: for code underneath the Inkscape namespace, you need only write GC::anchor(), but in other code you will need to write - Inkscape::GC::anchor(), or import the GC namespace with: + Inkscape::GC::anchor(), or import the GC namespace to your .cpp file + with: namespace GC = Inkscape::GC; @@ -48,9 +49,8 @@ you're done with it. This means that during the lifetime of an object, there should be N refs and N+1 unrefs on it. If these become unbalanced, then you are likely to -experience either transient crashing bugs (since the object could get freed -while someone is still using it) or memory leaks (the object is forgotten -while it still has a nonzero refcount, so it is never freed). +experience either transient crashing bugs (the object gets freed while +someone is still using it) or memory leaks (the object never gets freed). As a rule, an object should be unreffed by the same class or compilation unit that reffed it. Reffing or unreffing an object on someone else's behalf