This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of TS status.
Section: 6 [filesys.ts::fs.filesystem.synopsis], 15.32 [filesys.ts::fs.op.space] Status: TS Submitter: GB-4 Opened: 2014-01-20 Last modified: 2017-07-30
Priority: Not Prioritized
View all other issues in [filesys.ts::fs.filesystem.synopsis].
View all issues with TS status.
Discussion:
Addresses: filesys.ts
Use of the term a 'non-privileged' process. The comment for available in the struct space_info refers to: free space available to a non-privileged process. This seems quite specific to a POSIX implementation (on Windows, for instance, the equivalent data would be user-specific but not directly related to privilege)
Remove the comment and add a note to 15.32 [fs.op.space]: [Note: the precise meaning of available space is implementation dependent. — end note]
[2014-02-07, Beman Dawes comments]
"implementaton defined" and "operating system dependent"
are well defined terms in this TS, but "implementation dependent" is not well defined.
The meaning of available
is operating system dependent, so that's the form used
in the proposed wording.
[2014-02-07, Beman Dawes provides wording]
Proposed resolution:
Change 6 [fs.filesystem.synopsis]:
uintmax_t available;
// free space available to a non-privileged process
Add Remarks to 15.32 [fs.op.space]:
Remarks: The value of member
space_info::available
is operating system dependent. [Note:available
may be less thanfree
. — end note]