Boost C++ Libraries: Ticket #11639: document std's vs boost's chrono::steady_clock system-wideness discrepancy https://svn.boost.org/trac10/ticket/11639 <p> 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 </p> <pre class="wiki">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. </pre><p> As far as I know, the C++11 standard does not make this requirement. </p> <p> 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. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/11639 Trac 1.4.3 viboes Thu, 10 Sep 2015 17:51:21 GMT status changed https://svn.boost.org/trac10/ticket/11639#comment:1 https://svn.boost.org/trac10/ticket/11639#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">assigned</span> </li> </ul> <p> What is wrong on the text? what is different from the C++11 standard? </p> Ticket Sébastien Barthélémy <barthelemy@…> Fri, 11 Sep 2015 13:48:56 GMT <link>https://svn.boost.org/trac10/ticket/11639#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/11639#comment:2</guid> <description> <p> Replying to <a class="ticket" href="https://svn.boost.org/trac10/ticket/11639#comment:1" title="Comment 1">viboes</a>: </p> <blockquote class="citation"> <p> What is wrong on the text? what is different from the C++11 standard? </p> </blockquote> <p> boost doc says: "steady_clock class provides access to the <strong>system-wide</strong> steady clock." </p> <p> As far as I know, there is no promise in the standard that the steady_clock is system-wide. For instance the steady_clock epoch may be related to the process-creation. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>viboes</dc:creator> <pubDate>Fri, 11 Sep 2015 17:05:54 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/11639#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/11639#comment:3</guid> <description> <p> Boost.Chrono uses system wide monotonic clocks. Boost.Chrono has specific process clocks, SO I think that it is important to make the distiction. </p> <p> Should I remove "system-wide"? </p> </description> <category>Ticket</category> </item> <item> <dc:creator>viboes</dc:creator> <pubDate>Wed, 23 Sep 2015 23:04:41 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/11639#comment:4 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/11639#comment:4</guid> <description> <p> PING!!! </p> </description> <category>Ticket</category> </item> <item> <dc:creator>viboes</dc:creator> <pubDate>Sun, 25 Oct 2015 23:49:58 GMT</pubDate> <title>type changed https://svn.boost.org/trac10/ticket/11639#comment:5 https://svn.boost.org/trac10/ticket/11639#comment:5 <ul> <li><strong>type</strong> <span class="trac-field-old">Bugs</span> → <span class="trac-field-new">Support Requests</span> </li> </ul> <p> Moved to support until someone respond. </p> Ticket