Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!cmcl2!husc6!rutgers!lll-crg!lll-lcc!well!tenney
From: tenney@well.UUCP (Glenn S. Tenney)
Newsgroups: net.micro.amiga
Subject: Re: Pay for Performance
Message-ID: <1913@well.UUCP>
Date: Fri, 10-Oct-86 21:54:32 EDT
Article-I.D.: well.1913
Posted: Fri Oct 10 21:54:32 1986
Date-Received: Sat, 11-Oct-86 21:04:40 EDT
References: <1904@well.UUCP> <6165@topaz.RUTGERS.EDU>
Reply-To: tenney@well.UUCP (Glenn S. Tenney)
Organization: Whole Earth Lectronic Link, Sausalito CA
Lines: 19

Busy waiting, per se, is not ALWAYS a bad thing.  If you are expecting alot
of interrupts (say tracking a fast-moving mouse) the overhead of wait's
etc. might slow things down too much.  In the case of DPaint, when you are
w/in DPaint's window and it busy waits, WHO CARES!  You aren't usually
multi-tasking at that point, at least not much.  And when you want to
do something else, you go up to the menu bar which, as someone said, 
uses wait.

Just remember, there are many considerations.  There may be the "right"
way to do something, and then the efficient way.  Performance of the
application might take precedence to not busy waiting.  Then, there
are times when you might want to do your own multi-tasking (internally)
where you may not be able to use wait.

-- Glenn Tenney 
UUCP: {hplabs,glacier,lll-crg,ihnp4!ptsfa}!well!tenney
ARPA: well!tenney@LLL-CRG.ARPA        Delphi and MCI Mail: TENNEY
As Alphonso Bodoya would say... (tnx boulton)
Disclaimers? DISCLAIMERS!? I don' gotta show you no stinking DISCLAIMERS!