std::experimental::filesystem::last_write_time (3) - Linux Manuals
std::experimental::filesystem::last_write_time: std::experimental::filesystem::last_write_time
NAME
std::experimental::filesystem::last_write_time - std::experimental::filesystem::last_write_time
Synopsis
Defined in header <experimental/filesystem>
file_time_type last_write_time(const path& p); (1) (filesystem TS)
file_time_type last_write_time(const path& p, error_code& ec)
void last_write_time(const path& p, file_time_type new_time); (2) (filesystem TS)
void last_write_time(const path& p, file_time_type new_time, error_code& ec);
1) Returns the time of the last modification of p, determined as if by accessing the member st_mtime of the POSIX stat (symlinks are followed) The non-throwing overload returns file_time_type::min() on errors.
2) Changes the time of the last modification of p, as if by POSIX futimens (symlinks are followed)
Parameters
p - path to examine or modify
new_time - new modification time
ec - out-parameter for error reporting in the non-throwing overload
Return value
1) The time of the last modification of p
2) (none)
Exceptions
The overload that does not take a error_code& parameter throws filesystem_error on underlying OS API errors, constructed with p as the first argument and the OS error code as the error code argument. std::bad_alloc may be thrown if memory allocation fails. The overload taking a error_code& parameter sets it to the OS API error code if an OS API call fails, and executes ec.clear() if no errors occur. This overload has
noexcept specification:
noexcept
Notes
It is not guaranteed that immediately after setting the write time, the value returned by (1) is the same as what was passed as the argument to (2) because the file system's time may be more granular than file_time_type.
Example
// Run this code
Possible output:
See also
file_time_type (typedef)