www.delorie.com/archives/browse.cgi | search |
From: | werewolf AT stad DOT dsl DOT nl (Shadow Seeker) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: uclock trouble |
Date: | Sat, 29 May 1999 09:00:14 GMT |
Organization: | Shimmer Zone |
Lines: | 14 |
Message-ID: | <373eecd2.19697433@news.tudelft.nl> |
References: | <Pine DOT SUN DOT 3 DOT 91 DOT 990516135445 DOT 26252Y-100000 AT is> <373EBC8B DOT A6271397 AT enter DOT net> |
NNTP-Posting-Host: | willow.akira.tudelft.nl |
X-Trace: | news.tudelft.nl 927968214 19258 130.161.60.189 (29 May 1999 08:56:54 GMT) |
X-Complaints-To: | usenet AT news DOT tudelft DOT nl |
NNTP-Posting-Date: | 29 May 1999 08:56:54 GMT |
X-Newsreader: | Forte Free Agent 1.11/32.235 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
On Sun, 16 May 1999 08:39:39 -0400, Sean <sproctor AT enter DOT net> wrote: >int t = (int)uclock(); >while(t < 0x2000) >{ > printf("%i", t); > t = (int)uclock(); >} Well there you go then, I had the same problem with Uclock. Uclock is a 64 bit counter and an int is only 32 bit, with me the error was that about 20 minutes after the first call to uclock it would wrap around to minus a lot.... ShadSek
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |