To:	dj AT stealth DOT ctron DOT com (DJ Delorie)
Cc:	dolan AT fnoc DOT navy DOT mil, djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: clock() problems
Date:	Tue, 08 Nov 94 09:07:43 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>

> Perhaps we should set CLOCKS_PER_SEC (or whatever) to 1193046 ?

In my judgement, only if clock_t is going to be long long (64-bit).
It isn't reasonable, even if allowed by ANSI, for the program
elapsed time to overflow after about 40 minutes.  Most programs
which use clock(), especially on a PC, won't suspect such a
a disaster.  I bumped into it while helping a friend to compile
a chess-playing program, which relies on clock() to count time
left for the players' moves.  You can imagine what happens when
it started getting negative times...

- Raw text -