Created on 2009-01-07.00:00:00 last changed 161 months ago
Proposed resolution:
Change [time.clock.req]:
1 A clock is a bundle consisting of a
nativeduration, anativetime_point, and a function now() to get the current time_point. The origin of the clock's time_point is referred to as the clock's epoch. A clock shall meet the requirements in Table 56.2 ...
Table 56 — Clock requirements Expression Return type Operational semantics C1::rep An arithmetic type or a class emulating an arithmetic type The representation type of the nativeC1::duration.and time_point.C1::period ... ... C1::duration chrono::duration<C1::rep, C1::period> The nativeduration type of the clock.C1::time_point chrono::time_point<C1> or chrono::time_point<C2, C1::duration> The nativetime_point type of the clock. C1 and C2 shall refer to the same epoch....
[ Adopted at 2010-11 Batavia ]
[ Post-Rapperswil, Howard provides wording: ]
Moved to Tentatively Ready with revised wording from Howard Hinnant after 5 positive votes on c++std-lib.
[ 2010-03-28 Daniel synced wording with N3092 ]
[ 2009-11-18 Daniel adds: ]
I see that [thread.timedmutex.requirements]/3 says:
Precondition: If the tick period of rel_time is not exactly convertible to the native tick period, the duration shall be rounded up to the nearest native tick period.
I would prefer to see that adapted as well. Following the same style as the proposed resolution I come up with
Precondition: If the tick period of rel_time is not exactly convertible to the
nativetick period of the execution environment, the duration shall be rounded up to the nearestnativetick period of the execution environment.
[ 2009-10-23 Pete provides wording: ]
[ Batavia (2009-05): ]
Move to Open pending proposed wording from Pete.
[ 2009-05-10 Howard adds: ]
The standard uses "native" in several places without defining it (e.g. [lex.ccon]). It is meant to mean "that which is defined by the facility", or something along those lines. In this case it refers to the nested time_point and duration types of the clock. Better wording is welcome.
[time.clock.req] uses the word "native" in several places, but doesn't define it. What is a "native duration"?
History | |||
---|---|---|---|
Date | User | Action | Args |
2011-08-23 20:07:26 | admin | set | status: wp -> c++11 |
2010-11-24 14:01:03 | admin | set | messages: + msg5416 |
2010-11-14 13:10:57 | admin | set | status: voting -> wp |
2010-11-08 14:14:39 | admin | set | status: ready -> voting |
2010-10-21 19:06:53 | admin | set | messages: + msg4778 |
2010-10-21 19:06:53 | admin | set | status: open -> ready |
2010-10-21 18:28:33 | admin | set | messages: + msg4552 |
2010-10-21 18:28:33 | admin | set | messages: + msg4551 |
2010-10-21 18:28:33 | admin | set | messages: + msg4550 |
2010-10-21 18:28:33 | admin | set | messages: + msg4549 |
2010-10-21 18:28:33 | admin | set | messages: + msg4548 |
2010-10-21 18:28:33 | admin | set | messages: + msg4547 |
2009-01-07 00:00:00 | admin | create |