From: Hurd, Matthew (hurdm_at_[hidden])
Date: 2003-11-03 16:17:49
> From: Daniel Spangenberg [mailto:dsp_at_[hidden]]
> the current boost.thread library (My discussion concerns about
> the official 1.30 version) provides the non-copyable property of
> objects of mutex type. This is OK, but in the current development
> of named synchronization objects for inter-process synchronization
> the very question arises whether such an object should be
> swappable or not. Consider a complex object
I think the non-copyable semantics is appropriate as the mutex may be a
truly non-copyable OS related thing.
There is no reason why you can't have a reference or pointer to a mutex and
that can be swapped amongst your objects.
Does that solve your issue?
Susquehanna Pacific P/L
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk