Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!uunet!intercon!amanda@intercon.com
From: amanda@intercon.com (Amanda Walker)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Need info on multitasking capabilities on the mac
Message-ID: <1580@intercon.com>
Date: 29 Nov 89 00:43:56 GMT
References: <6391@tank.uchicago.edu> <9072@hoptoad.uucp> <17247@dartvax.Dartmouth.EDU> <9080@hoptoad.uucp> <1250@smurf.ira.uka.de> <10702@claris.com>
Sender: news@intercon.com
Reply-To: amanda@intercon.com (Amanda Walker)
Organization: InterCon Systems Corporation
Lines: 16

In article <10702@claris.com>, peirce@claris.com (Michael Peirce) writes:
> I agree with Matthias, setting up a protocol that only depends on completion
> routines isn't really all that painful.  You just have to understand how to
> program using state machines.

In fact, thinking of your code as a state machine is an extremely effective
technique for Macintosh programming in general, especially when I/O of any
sort is involved.  It makes a lot of potential difficulties evaporate (by,
of course, introducing others :-)).  In particular, it makes it much easier
to make the code friendly to other things going on at the same time, since
you don't spend any time waiting for stuff that hasn't happened yet.

--
Amanda Walker
InterCon Systems Corporation
amanda@intercon.com