From: William E. Kempf (williamkempf_at_[hidden])
Date: 2002-09-24 09:06:37
From: "Michael Glassford" <glassfordm_at_[hidden]>
> I've been examining and using the 1.28 version of Boost.Threads a lot over
> the past week or so and noticed that while "A TimedMutex is a refinement
> TryMutex", on the other hand "A ScopedTimedLock is a refinement of Lock"
> (not of TryLock). Is this intentional or an oversight?
Intentional, but confusing, and maybe not the best way to document what's
going on here. The ScopedTimedLock and ScopedTryLock constructors
intentionally conflict, which leads to the differing refinement paths.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk