Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!usc!apple!well!farren
From: farren@well.UUCP (Mike Farren)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice C 5.04 bug
Message-ID: <14996@well.UUCP>
Date: 13 Dec 89 23:35:11 GMT
References: <828@wet.UUCP> <12147@cbnewsc.ATT.COM>
Reply-To: farren@well.UUCP (Mike Farren)
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 16

In article <12147@cbnewsc.ATT.COM> gregg@cbnewsc.ATT.COM (gregg.g.wonderly) writes:
>From article <828@wet.UUCP>, by mcw@wet.UUCP (Martin Warnett):
>	Delay (60*n);
               ^^------- 50 * n, please - Delay works in 50ths of a second.

>the code was written with huge amounts of StartIO/WaitIO and other such
>nonsense.  This is really why the Exec functions were written.

Ahh - but Delay isn't an Exec function, it's a DOS function.  Personally,
I try to avoid using DOS functions whenever possible, on principle, mostly.
Huge amounts of StartIO/WaitIO implies usage of timer.device, which is
the approved, non-DOS, more accurate, and more flexible means of getting
a busyloop-free delay.  After all, you only have to design sleep() once...

-- 
Mike Farren 				     farren@well.sf.ca.usa