Re: [Boost-bugs] [Boost C++ Libraries] #8006: Boost::Chrono Assertion at startup

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8006: Boost::Chrono Assertion at startup
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-02-08 22:46:24


#8006: Boost::Chrono Assertion at startup
----------------------------------------+-----------------------------------
  Reporter: meckschlager@… | Owner: viboes
      Type: Bugs | Status: new
 Milestone: To Be Determined | Component: chrono
   Version: Boost 1.48.0 | Severity: Problem
Resolution: | Keywords:
----------------------------------------+-----------------------------------

Comment (by viboes):

 Replying to [comment:4 meckschlager@…]:
> Hi, thanks embracing that issue up!
>
> > Why do you think that the code is thread unsafe?
> It states so in the chrono users guide
> "All functions in the library are thread-unsafe except when noted
 explicitly."
> (http://www.boost.org/doc/libs/1_52_0/doc/html/chrono/users_guide.html)
> thats why I came to the working solution
>
> lock
> steady_clock::time_point now = steady_clock::now();
> unlock
>
> Now, it just seems unnecessary that multiple threads might have to wait
 to get the current time, which many os methods would return without
 requiring a lock.

 Hrr! I would fix this on the documentation, call to Clock::now() should be
 thread safe.

 Thanks for the report.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/8006#comment:5>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:11 UTC