From owner-freebsd-arch Fri Oct 26 18:24:49 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 281A937B401 for ; Fri, 26 Oct 2001 18:24:47 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f9R1bVv06321; Fri, 26 Oct 2001 18:37:31 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110270137.f9R1bVv06321@mass.dis.org> To: Dag-Erling Smorgrav Cc: arch@FreeBSD.ORG Subject: Re: 64 bit times revisited.. In-Reply-To: Message from Dag-Erling Smorgrav of "27 Oct 2001 03:06:00 +0200." Date: Fri, 26 Oct 2001 18:37:31 -0700 From: Mike Smith 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 > Mike Smith writes: > > These programs should *not* be trying to use these functions. These > > functions are meant for manipulating time_t, which is a > > representation of "now". > > Mike, we can't fix everybody else's broken software. What we *can* do > is fix *ours* so it plays nice with theirs. Our software doesn't need fixing. It works just fine, and just as it always has right now. This "fixing" you're talking about will introduce subtle and egregious problems in all manner of situations, and the amount of grief that it will cause will far outweigh any of the putative "benefits" that have been suggested so far. If there is a shift in the time_t paradigm, it's going to need to be driven by the industry at large, and it will need to be supported by wider consensus than a small frothing cabal such as currently stands behind this set of proposals. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message