Title
Make monotonic clocks mandatory
Status
resolved
Section
[time.clock.monotonic]
Submitter
Switzerland

Created on 2010-08-25.00:00:00 last changed 170 months ago

Messages

Date: 2011-05-21.21:15:19

Proposed resolution:

This is resolved by n3191.

Date: 2010-11-13.00:00:00

[ 2010-11-13 Batavia meeting: ]

This is resolved by adopting n3191. The original resolution is preserved for reference:

Make monotonic clocks mandatory.

Strike [time.clock.monotonic] p.2

2 The class monotonic_clock is conditionally supported.

Change [thread.req.timing] p.2 accordingly

The member functions whose names end in _for take an argument that specifies a relative time. Implementations should use a monotonic clock to measure time for these functions. [ Note: Implementations are not required to use a monotonic clock because such a clock may not be available. — end note ]

Date: 2010-11-01.00:00:00

[ 2010-11-01 Daniel comments: ]

Paper n3128 addresses this issue by replacing monotonic_clock with steady_clock, which is mandatory.

Date: 2010-10-24.03:04:13

Addresses CH-21

Monotonic clocks are generally easy to provide on all systems and are implicitely required by some of the library facilities anyway.

History
Date User Action Args
2010-11-18 12:46:23adminsetstatus: nad editorial -> resolved
2010-11-13 13:11:26adminsetmessages: + msg5353
2010-11-13 13:11:26adminsetstatus: open -> nad editorial
2010-11-01 19:22:54adminsetmessages: + msg5228
2010-10-26 12:06:53adminsetmessages: + msg5144
2010-10-24 03:04:13adminsetmessages: + msg4911
2010-08-25 00:00:00admincreate