Date: Sun, 15 Jun 1997 12:05:45 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Bob Kematick <rjkematick AT postoffice DOT worldnet DOT att DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: rawclock() and other time.h functions
In-Reply-To: <33A1480B.7AA@postoffice.worldnet.att.net>
Message-ID: <Pine.SUN.3.91.970615120514.14561M-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Fri, 13 Jun 1997, Bob Kematick wrote:

> than fix the function. As it is now, clock() and rawclock() seem
> quite similar. Redundant perhaps.

No, not redudant.  As far as I understand, `rawclock' is a
compatibility function, so you could port programs that use it to
DJGPP.

> > `rawclock' is not meant to be used as a randomizer, use `time' for
> > that.
> 
> time() returns a large integer which is the total number of seconds 
> since God knows when. One second resolution not so great in a fast 
> running program.

See my other message in this thread about these issues.