Message-ID: <374219A4.855835DB@vortex.ufrgs.br>
Date: Tue, 18 May 1999 22:53:40 -0300
From: "Luciano R. M. Silva" <lrms AT vortex DOT ufrgs DOT br>
X-Mailer: Mozilla 4.51 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: uclock trouble
References: <373DCBAB DOT DB9BC535 AT enter DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: prt16u39.ez-poa.com.br
Lines: 14
NNTP-Posting-Host: irc.ez-poa.com.br
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Sean,

I have used uclock and it works nice on DOS (under Win95 it can
have problems). Remember it returns a 64bit value (long long).
If you look at just the lower 16bits they really should (appear to)
overflow (can't find the more proper word) about every 54.8ms
(18.2 times per second). If you declare your values as uclock_t
(and also if your are not under Windows) it should work . Also
if you use it as an int (32 bit) value it should appear to overflow
(and return to zero) at every hour.

LRMS