Microsoft's documentation reports this, "
The parse method returns an integer value representing the number of
milliseconds between midnight, January 1, 1970 and the date supplied
Would that not imply that the above value should be ZERO?
Dr J R Stockton
In microsoft.public.scripting.jscript message <1182292689.337148.23170@o
61g2000hsh.googlegroups.com>, Tue, 19 Jun 2007 15:38:09, Ben
<(E-Mail Removed)> posted:
>Can anyone explain why this,
> Date.parse("Jan 1, 1970")
>Microsoft's documentation reports this, "
>The parse method returns an integer value representing the number of
>milliseconds between midnight, January 1, 1970 and the date supplied
>Would that not imply that the above value should be ZERO?
It would, but MS documentation should not be believed infallible.
You have 18000000 ms or 18000 sec or 300 min or 5 hours.
You, apparently being in New York or thereabouts, are five hours slow on
the real time, which is of course GMT.
Their "midnight, January 1, 1970" is ambiguous, because a day has two
midnights, and also wrong, because it implies local time.
The true zero is 1970-01-01 00:00:00 UT, to which UTC & GMT are good
approximations for the purpose.
Note - Microsoft probably copied the error, rather than originating it.
It's a good idea to read the newsgroup c.l.j and its FAQ. See below.
Like anybody who thinks Cristmas is the day
the sun shines 24 hours over the his square mile.
And the rest of the word of 6 Billion will suck up
to a militant and lying minority of ess than 100 million.
"Dave Anderson" <(E-Mail Removed)> wrote in message
> "Ben" wrote:
>> Can anyone explain why this,
>> Date.parse("Jan 1, 1970")
>> equals this,
> Your time zone accounts for the difference. Compare:
> Date.parse("Jan 1, 1970 EST") // 18000000
> Date.parse("Jan 1, 1970 GMT") // 0
> Dave Anderson
> Unsolicited commercial email will be read at a cost of $500 per message.
> Use of this email address implies consent to these terms.