From: Bob Kematick <rjkematick AT postoffice DOT worldnet DOT att DOT net>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: rawclock() and other time.h functions
Date: Fri, 13 Jun 1997 08:15:55 -0500
Organization: myhouse
Lines: 25
Message-ID: <33A1480B.7AA@postoffice.worldnet.att.net>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970612181819 DOT 9257V-100000 AT is>
NNTP-Posting-Host: 207.146.35.217
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Eli Zaretskii wrote:
> 
> On Wed, 11 Jun 1997, Nate Eldredge wrote:
> 
> > This works for me. It's theoretically possible that something depends on the
> > broken version, and this would break that. But I seriously doubt it.
> >
> > Perhaps a fix like this should be made to the next DJGPP release.
> 
> The bug is in the docs, not in the code.  The next release will fix
> the docs.
> 

Eli : 

Could you comment on why it is preferable to fix the docs rather
than fix the function. As it is now, clock() and rawclock() seem
quite similar. Redundant perhaps.

> `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.