To: eliz AT is DOT elta DOT co DOT il, djgpp AT delorie DOT com Date: Thu, 12 Jun 1997 17:03:13 -0700 Subject: Re: rawclock() and other time.h functions Message-ID: <19970612.170431.8822.3.bshadwick@juno.com> References: From: bshadwick AT juno DOT com (Ben N Shadwick) Precedence: bulk On Thu, 12 Jun 1997 18:18:45 +0300 (IDT) Eli Zaretskii writes: >> 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. I don't believe you. What good does a bunch of functions that always return zero the first time you call them do (besides giving you four hundred ways to measure how fast your program is)? IMHO, they have many more applications when implemented the way the docs describe them - if you need to use it the "returns-zero-the-first-time" way, just set some variable equal to it and subtract its value to achieve the same effect. On the other hand, if you need a quick way to know the number of seconds (or clock ticks) since midnight, you have that too. >`rawclock' is not meant to be used as a randomizer, use `time' for >that. Like Nate said, it only has a 1 second accuracy that way (not very desirable) ===== Ben Shadwick, Sysop, Mars Base BBS, (360)882-0773, Vancouver, WA, USA Unofficial member, TheGods/DemiUrg Software, http://www.swiftsite.com/thegods email: bshadwick AT juno DOT com (please reply to newsgroup posts via email too)