[Aptitude-svn-commit] r4151 - branches/aptitude-0.3/aptitude

[Daniel Burrows]

Author: dburrows
Date: Wed Sep 21 20:12:44 2005
New Revision: 4151

Modified:
   branches/aptitude-0.3/aptitude/README.SMART-POINTERS
Log:
Update the smart pointers documentation again.

Modified: branches/aptitude-0.3/aptitude/README.SMART-POINTERS
==============================================================================
--- branches/aptitude-0.3/aptitude/README.SMART-POINTERS	(original)
+++ branches/aptitude-0.3/aptitude/README.SMART-POINTERS	Wed Sep 21 20:12:44 2005
@@ -7,6 +7,18 @@
 safely, but C++ being what it is, you should be aware of how they work
 and what the caveats are.
 
+  * threading
+
+  As of this writing, none of the smart pointers lock their reference
+  counts (implementing locks in the imm::wtree class caused the
+  problem resolver's running time to increase by 50%!).  Some of the
+  less-commonly-used ones may get locking in the future, but for the
+  time being you should handle objects that are given to another
+  thread carefully -- do deep copies of anything that's
+  reference-counted.  (this is only the imm::* stuff at the moment, so
+  the problem is managable) For more information on threading, see
+  README.THREADS.
+
   * reference-counted immutable values
 
   aptitude employs reference-counting of immutable objects in several
@@ -40,7 +52,6 @@
   be created, it's always safe to reference-count objects like this.
 
 
-
   * auto_ptr for temporary return values
 
   When building up a temporary return value, several routines use