From owner-freebsd-arch Fri Oct 26 10:50:19 2001 Delivered-To: freebsd-arch@freebsd.org Received: from marlborough.cnchost.com (marlborough.concentric.net [207.155.248.14]) by hub.freebsd.org (Postfix) with ESMTP id 4AC4B37B403 for ; Fri, 26 Oct 2001 10:50:18 -0700 (PDT) Received: from bitblocks.com (adsl-209-204-185-216.sonic.net [209.204.185.216]) by marlborough.cnchost.com id NAA29175; Fri, 26 Oct 2001 13:50:10 -0400 (EDT) [ConcentricHost SMTP Relay 1.14] Message-ID: <200110261750.NAA29175@marlborough.cnchost.com> To: Poul-Henning Kamp , Peter Wemm , arch@FreeBSD.ORG Subject: Re: 64 bit times revisited.. In-reply-to: Your message of "Fri, 26 Oct 2001 10:48:10 PDT." <200110261748.NAA22627@rodney.cnchost.com> Date: Fri, 26 Oct 2001 10:50:10 -0700 From: Bakul Shah Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I wrote: > need it in some form. So, just like ascii (char) and unicode > (wchar_t), why define a _new_ time type and insist people > start using that for new software? Then the current time_t > is valid only in the first "epoch". The second line should be: (wchar_t), why not define a _new_ time type and insist people Sorry! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message