$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: Michael Glassford (glassfordm_at_[hidden])
Date: 2004-06-23 10:51:03
The Boost.Threads documentation states that the ScopedTimedLock concept
is a refinement of the ScopedTryLock concept; however, the
boost::timed_mutex::scoped_timed_lock class, which is supposed to be a
model of the ScopedTimedLock concept, doesn't define the various try_*
methods.
In your opinion, should the documentation be changed to state that the
ScopedTimedLock concept is a refinement of the ScopedLock (rather than
ScopedTryLock) concept, or should the
boost::timed_mutex::scoped_timed_lock class implement the various try_*
methods?
(FYI: a similar situation applies to
boost::recursive_timed_mutex::scoped_timed_lock and
boost::timed_read_write_mutex::scoped_timed_lock).
Mike