From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9fbc059a74d74032 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-05-30 19:03:09 PST Newsgroups: comp.lang.ada Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!paloalto-snf1.gtei.net!news.gtei.net!news.compaq.com!uunet!sac.uu.net!ash.uu.net!world!bobduff From: Robert A Duff Subject: Re: Leap Seconds Sender: bobduff@world.std.com (Robert A Duff) Message-ID: Date: Thu, 31 May 2001 02:01:18 GMT References: <9elpii$30i$1@nh.pace.co.uk> <3B0ED67B.E40A4E06@averstar.com> <9f0ciq$itb$1@nh.pace.co.uk> <9f2ue6$hcm$1@nh.pace.co.uk> <9f347i$jo1$1@nh.pace.co.uk> Organization: The World Public Access UNIX, Brookline, MA X-Newsreader: Gnus v5.3/Emacs 19.34 Xref: archiver1.google.com comp.lang.ada:7906 Date: 2001-05-31T02:01:18+00:00 List-Id: "Marin David Condic" writes: > In any case, my point was that your watch and my watch can both be ticking > off seconds in relative synch even though my watch says "4:30am, Tuesday" > {actually it doesn't "say" anything - you have to look at it.} and your > watch says "3:15pm, Wednesday" You can therefore safely ignore leap-seconds > and leap-years as long as all we're doing is saying "Let's meet for a beer > at Ruby Tuesdays in The Gardens Mall, Palm Beach Gardens, FL (free plug > there, guys!) in one hour, thirty two minutes and 15 seconds." As long as no > leap-seconds or leap-years happen between now and then, we're fine > (depending on traffic). I don't get it. If we both agree on when the epoch is, and we have a way of counting seconds since the epoch, then we can agree to meet for beer at 1,234,567,890.0 seconds after the epoch. It doesn't matter that my clock shows a different time than yours (because I count leap seconds and you don't, or because I don't believe in "nightdark wasting time", or because we're in different time zones, or whatever). Isn't all the leap-seconds business about converting to/from a human readable form. I mean, leap seconds are exactly one-second long, just like any other seconds. (Unlike leap years, which are longer than other years.) By the way, it seems to me that Ada *forbids* counting leap seconds, in that the upper bound of Day_Duration is 86_400.0, rather than 86_401.0. True? > Time can be a *very* confusing business! Indeed. - Bob