If the threads don't modify the tree you could use the yield-iterator - otherwise you would have to protected the tree against modifications anyway. The yield-iterator can be used if the tree is shared between several threads. If you don't use thread-specific storage you could move the iterator from on thread to another (but you can't use it in multiple threads at the same time -> critical section). Oliver -------- Original-Nachricht --------
Datum: Tue, 21 Jun 2011 10:12:48 +0800 Von: Sylvain Bougerel <sylvain.bougerel.devel@gmail.com> An: boost@lists.boost.org Betreff: Re: [boost] [yield_iterator] new iterator lib with C# yield return/yield break
On Jun 21, 2011 2:15 AM, "Oliver Kowalke" <oliver.kowalke@gmx.de> wrote:
For instance iterating an tree would usally require to traverse the complete tree and store the nodes in a STL container - the begin/end iterators of this STL container are used to iterate the tree.
I'm under the impression that we generally iterate through trees by pointing the iterator to the node of the tree, instead of storing everything into a stack.
I would probably have to do this if the tree was an object shared across several threads. Is this meant for this type of usage?
Cheers, Sylvain _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- NEU: FreePhone - kostenlos mobil telefonieren! Jetzt informieren: http://www.gmx.net/de/go/freephone