Re: NSFileModificationDate after 2039
Re: NSFileModificationDate after 2039
- Subject: Re: NSFileModificationDate after 2039
- From: "Sean McBride" <email@hidden>
- Date: Tue, 26 Apr 2005 14:37:35 -0400
- Organization: Rogue Research
On 2005-04-26 11:19, Shawn Erickson said:
>> Some further investigation showed:
>
>[snipped an excellent listing of issues]
Indeed! Additionally, I really do suggest bringing this up on say
darwin-dev (<http://lists.apple.com/mailman/listinfo/darwin-dev>) people
there may have useful workarounds/comments. I believe it would be
ontopic there as these bugs are to do with HFS and BSD APIs, though it
does touch Cocoa too.
One more comment though:
On 2005-04-26 19:22, Gerriet M. Denkmann said:
>Some further investigation showed:
>
>TN1150 says "The maximum representable date [of an HFS+ file] is
>February 6, 2040 at 06:28:15 GMT".
>
> SNIP
>
>5. No-one seems to have told the Finder (poor thing) that it is now
>living in a Unix world - it displays the HFS+ value of 0xffffffff as 6.
>Feb. 2040 6:28 GMT (should be 1903-12-31 23:59:59 +0000)
No, the Finder is right here. HFS dates are 1904-based and so 0xffffffff
(the max date) should be Feb. 2040 6:28 GMT.
>and it treats
>the HFS+ value of 0x0 as undefined and displays "--".
Seems it should show 1904-01-01 here.
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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