From owner-freebsd-bugs Wed Sep 5 9:35:25 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from christel.heitec.net (christel.heitec.net [193.101.232.3]) by hub.freebsd.org (Postfix) with ESMTP id D550037B406 for ; Wed, 5 Sep 2001 09:35:23 -0700 (PDT) Received: from heitec.net (paladin.heitec.net [193.101.232.30]) by christel.heitec.net (Postfix) with ESMTP id 66598B8101; Wed, 5 Sep 2001 18:35:22 +0200 (CEST) Date: Wed, 05 Sep 2001 18:35:22 +0200 From: Bernd Luevelsmeyer X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: Bruce Evans Cc: David Malone , freebsd-bugs@FreeBSD.ORG Subject: Re: misc/30297: CLOCKS_PER_SEC non-standard References: <20010906011650.T24132-100000@alphplex.bde.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010905163522.66598B8101@christel.heitec.net> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bruce Evans wrote: [...] > More because it would break binary compatibilty. I wanted to change > CLOCKS_PER_SEC to 1 million many years ago (clocks.7 says a little > about this), but didn't want to face the binary compatibilty issues. > clock_t would have to be int64_t or uint64_t... That's worse than I thought; in fact I didn't consider that with 1000000 units per second and 32 bits to count you get only 0.05 days, a little more than one hour. That's of course impossible, but widening clock_t to 64 bits is also stupid if it's done just for the conformance, without helping the resolution at all. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message