[Boost-bugs] [Boost C++ Libraries] #11639: document std's vs boost's chrono::steady_clock system-wideness discrepancy

Subject: [Boost-bugs] [Boost C++ Libraries] #11639: document std's vs boost's chrono::steady_clock system-wideness discrepancy
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2015-09-10 08:20:34

#11639: document std's vs boost's chrono::steady_clock system-wideness discrepancy
-------------------------------------------------+---------------------
 Reporter:  Sébastien Barthélémy <barthelemy@…>  |      Owner:  viboes
     Type:  Bugs                                 |     Status:  new
Milestone:  To Be Determined                     |  Component:  chrono
  Version:  Boost 1.59.0                         |   Severity:  Problem
 Keywords:                                       |
-------------------------------------------------+---------------------
 boost doc states that its steady_clock is system-wide, in
 doc/libs/1_59_0/doc/html/chrono/reference.html#chrono.reference.cpp0x.system_clocks_hpp.steady_clock
 {{{
 steady_clock class provides access to the system-wide steady clock.
 The current time can be obtained by calling steady_clock::now().
 There is no fixed relationship between values returned by
 steady_clock::now() and wall-clock time.
 }}}

 As far as I know, the C++11 standard does not make this requirement.

 It would be good to highlight this discrepancy in the doc, especially
 since the doc "Included on the C++11 Recommendation" section let's you
 think that boost's chrono and std's chrono are interchangeable.

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