From owner-freebsd-hackers Sun Aug 16 15:46:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02236 for freebsd-hackers-outgoing; Sun, 16 Aug 1998 15:46:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02224 for ; Sun, 16 Aug 1998 15:46:19 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40345>; Mon, 17 Aug 1998 08:45:21 +1000 Date: Mon, 17 Aug 1998 08:45:34 +1000 From: Peter Jeremy Subject: Re: 64-bit time_t To: hackers@FreeBSD.ORG Message-Id: <98Aug17.084521est.40345@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Aug 1998 13:52:29 +0200, Andre Oppermann wrote: >TAI64 looks good (quotes from DJB's definition): > > "TAI stands for Temps Atomique International, the current international > real time standard." Switching from UTC to TAI opens up a whole new can of worms. In particular: 1) AFAIK, civil time is derived from UTC. 2) It is not possible to accurately convert a future time between TAI and UTC (because the offset between TAI and UTC depends on the _measured_ decay in the Earth's rotation). That said, when we do move to a 64-bit time_t, TAI64 would be a reasonable choice. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message