NSFileModificationDate after 2039
NSFileModificationDate after 2039
- Subject: NSFileModificationDate after 2039
- From: "Gerriet M. Denkmann" <email@hidden>
- Date: Mon, 25 Apr 2005 10:04:37 +0200
I have a file on HFS+ which has contentModDate (u_int32_t) =
0xffffffff.
This should be: 2040-02-06 07:28:15 +0100.
(see HFSPlusCatalogFile in /usr/include/hfs/hfs_format.h)
But fileAttributesAtPath:traverseLink: returns:
NSFileModificationDate = 1904-01-01 00:59:59 +0100;
That is: the NSFileManager reads the unsigned value from HFS+ as a
signed -1.
Is this a bug, or am I missing something?
Also, when I try to set the modification date to any date after
"2038-01-19 03:14:07 +0000" the date gets replaced with "1904-01-01
00:00:00 +0000" - but changeFileAttributes: does not return an error.
What is so special about "2038-01-19 03:14:07 +0000" ? Is this the
date where the world will end?
HFS+ can do dates up to: "2040-02-06 06:28:15 +0000" - why does
NSFileManager refuses to set some dates? Is this documented somewhere?
Kind regards,
Gerriet.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden