Re: NSTimestamp bug??
Re: NSTimestamp bug??
- Subject: Re: NSTimestamp bug??
- From: Chuck Hill <email@hidden>
- Date: Mon, 5 Apr 2004 09:14:58 -0700
Time. Shudder. I'm a little fearful of stepping into this, but
anyway...
I think what you are seeing is a bug in the documentation. The
behavior you are seeing is exactly what I would expect (not what I'd
*want* but what I've come to expect). These classes are focused on
accuracy in time calculations not conforming to our colloquial usage.
A day is 24 hours. Clock time (as you intended it) is not preserved
across DST boundries, timezones, and other changes in the counting of
time.
The only way I know of to do this is to construct a date manually from
the pieces of another.
Chuck
On Apr 5, 2004, at 8:25 AM, Tom Pelaia wrote:
It appears to me that the timestampByAddingGregorianUnits() method of
NSTimestamp does not properly handle changing by day increments. The
documentation claims that the method preserves "clock time" across
daylight savings changes, but that doesn't appear to be happening in
my application. Instead when I start from 00:00 on today (Monday) and
go back one day I get 23:00 on Saturday. Has anyone else seen this
issue or does it indicate something wrong with the system clock on our
server?
thanks,
-tom
--
Tom Pelaia
SNS Project, 701 Scarboro Road, MS-6473, Oak Ridge, TN 37830
phone: (865)574-6421, fax: (865)574-6617
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.