Thanks I just stumbled on that earlier today. It confounds me that the
parameter is renamed from VoidPointer to VoidMutex ???!!!
that is basically how I missed it. I thought there was some inscurtable
argument deduction going on.
Thanks so much Gevorg.
----- Original Message -----
From: "Gevorg Voskanyan"
Eric Whitcombe wrote:
I am stepping through interprocess shared memory code and I was a little confused by the offset_ptr code that I was hitting*. I cannot figure out how that is specified to the template of rbtree_best_fit. I see in boost/interprocess/interprocess_fwd.hpp the declaration of managed_shared_memory by typedef'ing basic_managed_shared_memory with rbtree_best_fit
as the AllocationAlgorithm argument but I can't figure out how offset_ptr is is supplied as the VoidPointer >>> argument to the rbtree_best_fit template. That template has 3 arguments but the forward declaration only provides one. Are the other two somehow inferred? If so, how? rbtree_best_fit
works because rbtree_best_fit class template's declaration specifies default arguments for VoidMutex and MemAlignment template parameters, shown here: template class rbtree_best_fit; So rbtree_best_fit
is equivalent to rbtree_best_fit Does that answer your question, or have I misunderstood it?
HTH, Gevorg _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users