Date: Wed, 1 Jan 1997 13:02:27 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Daniel Everton <evos AT m140 DOT aone DOT net DOT au>
cc: djgpp AT delorie DOT com
Subject: Re: problems with rawclock()
In-Reply-To: <5ad8s8$758_001@cpe.Maroochydore.aone.net.au>
Message-ID: <Pine.SUN.3.91.970101130112.16397A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Wed, 1 Jan 1997, Daniel Everton wrote:

> supposed to. According to the libc.inf file rawclock() "Returns the 
> number of clock tics (18.2 per second) since midnight." Yet when I use 
> it I find that it always returns zero. Anybody know what's going on?

This is a bug in the docs, rawclock is supposed to work the way it does.  
Don't use it to seed random numbers, use time().