[prev in list] [next in list] [prev in thread] [next in thread] 

List:       boost-bugs
Subject:    [Boost-bugs] [Boost C++ Libraries] #6339: timed_lock functionality
From:       "Boost C++ Libraries" <noreply () lists ! boost ! org>
Date:       2011-12-31 15:25:03
Message-ID: 072.f61799ce4f3a0f6e5d6cb1b290f38b4e () lists ! boost ! org
[Download RAW message or body]

#6339: timed_lock functionality should also take a time duration
-----------------------------------------------------+----------------------
 Reporter:  Edward Diener <eldiener@…>               |       Owner:  igaztanaga  
     Type:  Feature Requests                         |      Status:  new         
Milestone:  To Be Determined                         |   Component:  interprocess
  Version:  Boost 1.48.0                             |    Severity:  Optimization
 Keywords:  timed_lock                               |  
-----------------------------------------------------+----------------------
 Interprocess use of locking functionality for scoped_lock expresses a
 timed_lock in terms of an absolute boost::posix_time::ptime time. It
 should also support a time duration from the current time when the
 scoped_lock is constructed. It can use the
 boost::posix_time::time_duration class for this.

 For compatibility with C++11 it should also use boost::chrono, both for an
 absolute time and for a time duration.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/6339>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.
_______________________________________________
Boost-bugs mailing list
Boost-bugs@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-bugs

[prev in list] [next in list] [prev in thread] [next in thread]