From owner-freebsd-arch Sat Jun 2 23:43: 2 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 77F2037B422 for ; Sat, 2 Jun 2001 23:42:59 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f536gi144612; Sun, 3 Jun 2001 08:42:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: arch@FreeBSD.ORG, drosih@rpi.edu Subject: Re: time_t definition is wrong In-Reply-To: Your message of "Sat, 02 Jun 2001 13:43:15 PDT." <200106022043.f52KhFh35078@vashon.polstra.com> Date: Sun, 03 Jun 2001 08:42:44 +0200 Message-ID: <44610.991550564@critter> From: Poul-Henning Kamp 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 In message <200106022043.f52KhFh35078@vashon.polstra.com>, John Polstra writes: >I'd prefer to keep it as "long" at least on the i386, because that's >what the type was for years before ANSI renamed it to "time_t". That, in my mind, is actually a good argument for making it "int" so that we can flush out those places which don't use time_t well in advance of the unaviodable change to >32 bits... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message