Issue with Date.parse and 10/29/2001

[Need Top Programmer]

Has anyone else encountered this issue? When you do Date.parse(date1)
and date1=10/29/2001 it seems to add an an additional 3600000 ms for
no reason.


Thanks,

Edward

 

[Lee]

Need Top Programmer said:

Has anyone else encountered this issue? When you do Date.parse(date1)
and date1=10/29/2001 it seems to add an an additional 3600000 ms for
no reason.

It doesn't happen to me, but then we don't do Daylight Saving Time.

 

[Lasse Reichstein Nielsen]

Has anyone else encountered this issue? When you do Date.parse(date1)
and date1=10/29/2001 it seems to add an an additional 3600000 ms for
no reason.

It's daylight saving. The date 10/28/2001 (apparently mm/dd/yyyy
format) is the Sunday where daylight saving were dropped, so it was 25
hours long (in local time).

/L

 

[Dr John Stockton]

JRS: In article <[email protected]>, seen
in Need Top Programmer

Has anyone else encountered this issue? When you do Date.parse(date1)
and date1=10/29/2001 it seems to add an an additional 3600000 ms for
no reason.

You cannot predict what happens when "you" do it; News is an
international medium, and includes people from all sorts of places,
perhaps including Australia, Hawaii, and parts of Arizona and of
southern Indiana. Whatever you mean by the above, people using systems
correctly configured for those places will not see a 3600 second change
of that nature near that date.

When asking date/time related questions, it is prudent to state one's
locality, if that is not obvious.

In the EU, what happens at around that date is not that something is
added; it is that 3600 seconds - the Summer Time offset - is no longer
being subtracted; in Autumn, we need to retard clocks that keep civil
time.

See below.