Issue 2608: [filesys.ts] [PDTS] file_time_type underspecified

Title: [filesys.ts] [PDTS] file_time_type underspecified
Status: open
Section: [fs.filesystem.synopsis]
Submitter: CH-7

Created on 2014-01-20.00:00:00 last changed 90 months ago

Messages

msg7720 (view)

Date: 2016-01-28.01:00:35

Proposed resolution:

Modify 6 [fs.filesystem.synopsis] as indicated:
```
    typedef chrono::time_point<unspecified-trivial-clock>  file_time_type;
  
```
~~unspecified-~~trivial-clock is an ~~unspecified type provided by the implementation~~ implementation-defined type that satisfies the TrivialClock requirements (~~C++11~~ISO 14882:2011 §20.12.3) and that is capable of representing and measuring file time values. Implementations should ensure that the resolution and range of file_time_type reflect the operating system dependent resolution and range of file time values.

msg7719 (view)

Date: 2014-02-13.00:00:00

[ 2014-02-13 LWG/SG-3 Issaquah: Proposed wording accepted. ]

msg7718 (view)

Date: 2014-02-11.00:00:00

[ 2014-02-11 Issaquah: (1)Implementation-defined. See wiki notes for rationale. (2) Leave other additions in place, but insert "the" before "resolution" (3) Strike "unspecified-" from "unspecified-trivial-type" in two places. Beman to provide wording for review next meeting. ]

msg7717 (view)

Date: 2014-02-15.00:00:00

[ 2014-02-10, Daniel suggests wording ]

msg7716 (view)

Date: 2016-01-31.20:31:05

Addresses: filesys.ts

Must the file_time_type hold times before 1960 and after 2050?

Specify the requirements to unspecified-trivial-clock for file_time_type.

History
Date	User	Action	Args
2017-07-30 20:10:41	admin	set	status: wp -> open
2016-01-28 01:00:35	admin	set	messages: + msg7720
2016-01-28 01:00:35	admin	set	messages: + msg7719
2016-01-28 01:00:35	admin	set	messages: + msg7718
2016-01-28 01:00:35	admin	set	messages: + msg7717
2014-01-20 00:00:00	admin	create