Accounting for leap seconds for "this time value"
mike.mcglothlin at gmail.com
Thu Sep 3 10:57:50 UTC 2015
Wouldn't the leap seconds be only formatting for display where as time stored in epochs is universal? If I'm on Mars the epochs value is the same whereas local time (on Mars) may have a totally different set of adjustments to keep the human readable time true to that planets rotation etc.
📱 Michael McGlothlin
> On Sep 3, 2015, at 5:06 AM, Claude Pache <claude.pache at gmail.com> wrote:
> That means that `Date.now()/1000` is the [Unix time] (https://en.wikipedia.org/wiki/Unix_time), which can't represent leap seconds. In particular, each minute is assumed to have exactly 60 seconds, and thus it is impossible to represent `1981-06-30 23:59:60 UTC` in JS (or in Unix time).
>> Le 3 sept. 2015 à 11:40, Karl Cheng <qantas94heavy at gmail.com> a écrit :
>> The current specification has this to say about the time value in dates:
>>> "Time is measured in ECMAScript in milliseconds since 01 January, 1970 UTC. In time values leap seconds are ignored. It is assumed that there are exactly 86,400,000 milliseconds per day."
>> What I would like to seek clarification about is if we were to do the following:
>> Math.floor(Date.now() / 1000) % 60;
>> es-discuss mailing list
>> es-discuss at mozilla.org
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss