pub struct ObjectTimes {
pub access: u32,
pub modification: u32,
pub change: u32,
pub birth: u32,
}Expand description
The four times a version-2 object header stores, in the order
H5O__cache_serialize writes them: seconds since the epoch, as H5_now
produces them.
Their presence is the H5O_HDR_STORE_TIMES flag — see
ObjectHeader::times — so an object created with
H5Pset_obj_track_times(true) cannot be encoded with the flag set and no
times behind it.
Fields§
§access: u32Access time (oh->atime).
modification: u32Modification time (oh->mtime).
change: u32Change time (oh->ctime).
birth: u32Birth time (oh->btime).
Implementations§
Source§impl ObjectTimes
impl ObjectTimes
Sourcepub fn created_at(now: u32) -> Self
pub fn created_at(now: u32) -> Self
All four set to now — what H5O_create_ohdr does for an object
created with timestamps enabled.
Sourcepub fn touched(self, now: u32) -> Self
pub fn touched(self, now: u32) -> Self
These times after a real modification of the object.
H5O_touch_oh moves access and change time to now for a version-2
header and leaves modification and birth time as they were — the
modification time is what its own XXX comment says is not updated
yet. Following it means a rewrite reports the same times libhdf5 would.