Boost C++ Libraries: Ticket #6339: timed_lock functionality should also take a time duration https://svn.boost.org/trac10/ticket/6339 <p> 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. </p> <p> For compatibility with C++11 it should also use boost::chrono, both for an absolute time and for a time duration. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/6339 Trac 1.4.3 Markus Mathes <Markus.Mathes@…> Tue, 06 Aug 2013 12:26:16 GMT <link>https://svn.boost.org/trac10/ticket/6339#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/6339#comment:1</guid> <description> <p> The same applies for interprocess_condition </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Ion Gaztañaga</dc:creator> <pubDate>Thu, 30 Jun 2016 20:26:44 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/6339#comment:2 https://svn.boost.org/trac10/ticket/6339#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">wontfix</span> </li> </ul> <p> Closing the bug as users have not shown interest in this feature. Interprocess follows POSIX's convention here using absolute timeouts. </p> Ticket