Opened 3 years ago

Last modified 3 years ago

#11639 assigned Support Requests

document std's vs boost's chrono::steady_clock system-wideness discrepancy

Reported by: Sébastien Barthélémy <barthelemy@…> Owned by: viboes
Milestone: To Be Determined Component: chrono
Version: Boost 1.59.0 Severity: Problem
Keywords: Cc:

Description

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.

Change History (5)

comment:1 Changed 3 years ago by viboes

Status: newassigned

What is wrong on the text? what is different from the C++11 standard?

comment:2 in reply to:  1 Changed 3 years ago by Sébastien Barthélémy <barthelemy@…>

Replying to viboes:

What is wrong on the text? what is different from the C++11 standard?

boost doc says: "steady_clock class provides access to the system-wide steady clock."

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.

comment:3 Changed 3 years ago by viboes

Boost.Chrono uses system wide monotonic clocks. Boost.Chrono has specific process clocks, SO I think that it is important to make the distiction.

Should I remove "system-wide"?

comment:4 Changed 3 years ago by viboes

PING!!!

comment:5 Changed 3 years ago by viboes

Type: BugsSupport Requests

Moved to support until someone respond.

Note: See TracTickets for help on using tickets.