From 551da380f9124d13d80fecfbd3f7031da6134361 Mon Sep 17 00:00:00 2001 From: mental Date: Sat, 29 Apr 2006 18:46:49 +0000 Subject: [PATCH] clarify wording --- doc/refcounting.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/refcounting.txt b/doc/refcounting.txt index a27fb21fb..e409262db 100644 --- a/doc/refcounting.txt +++ b/doc/refcounting.txt @@ -69,7 +69,7 @@ breaks down in the presence of objects that reference each other. Common examples are elements in a doubly-linked list with "prev" and "next" pointers, and nodes in a tree, where a parent keeps a list of children, and children keep a pointer to their parent. If both cases, if there is a "ref" -in both directions, neither parent nor children can ever get freed. +in both directions, neither object can ever get freed. Because of this, circular data structures should be avoided when possible. When they are necessary, try only "reffing" in one direction -- 2.30.2