Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!decwrl!shelby!polya!ali From: ali@polya.Stanford.EDU (Ali T. Ozer) Newsgroups: comp.sys.amiga Subject: Re: Attention Programmers Message-ID: <9981@polya.Stanford.EDU> Date: 13 Jun 89 03:34:16 GMT References: <365@xdos.UUCP> <8895@phoenix.Princeton.EDU> <89158.094143UH2@PSUVM> Sender: Ali T. Ozer Reply-To: aozer@NeXT.com (Ali Ozer) Organization: . Lines: 22 In article <89158.094143UH2@PSUVM> UH2@PSUVM.BITNET (Lee Sailer) writes: > ... Also important, on the Amiga you have to learn some >tricks about multi-tasking, that is you want your program to cooperate >with other programs that might be running. I'm not sure I agree with this; as long as you follow common sense programming (or what I consider common sense programming 8-), you do not need to learn any tricks about multitasking. The phrase "on the Amiga you have to learn some tricks about multi-tasking, that is if you want your program to cooperate with other programs that might be running" is more true for the Macintosh Multifinder environment than it is for the Amiga. Rules for common sense programming include "manage your resources," and don't "busy-wait." On the Amiga "managing your resources" might be somewhat tougher than on a Unix machine, but not much tougher. Of course if you do decide to have your program talk with other programs or have your program spawn off tasks to do things, then you will need to learn about multitasking and message passing and so on. But that is only if you want to make explicit use of these features. Ali Ozer