Date: Mon, 7 Nov 94 23:02:41 -0500
From: dj AT stealth DOT ctron DOT com (DJ Delorie)
To: sandmann AT new-orleans DOT NeoSoft DOT com
Cc: dolan AT fnoc DOT navy DOT mil, djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: clock() problems


The reason why we can use clock() at up to 1.19 MHz is because the
hardware keeps track of it for us.  All we have to do is *calculate*
the return value of clock() when it's called.  We don't actually have
to get interrupted on each tic.

Compatibility isn't an issue; apps will always link with the library
that goes with the header they included (we hope).  This is a good
change to think about for V2.0.