|
Boost : |
From: Jason Hise (chaos_at_[hidden])
Date: 2005-01-11 17:51:32
Alexander Terekhov wrote:
>http://groups.google.de/groups?selm=3EC3AA39.7126DCCC%40web.de
>http://groups.google.de/groups?selm=3ECBD751.8DE8AED5%40web.de
>http://groups.google.de/groups?selm=4049DF28.BFEDCD0A%40web.de
>http://groups.google.de/groups?selm=410280D4.F18B3B87%40web.de
>http://groups.google.de/groups?selm=412533CA.82703A04%40web.de
>http://groups.google.de/groups?selm=41C301DF.5B50EDB7%40web.de
>
Thanks for the links. However, I am not looking to use a threading
library... instead, I only want to provide a hook for client code to
use. What I am mainly looking for is a good interface for a thread
safety mechanism. Then I can let client code deal with the details. Is
requiring empty lock and unlock methods adequate, or are there other
safety mechanisms that should be included?
-Jason
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk