Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!labrea!polya!gilham
From: gilham@polya.Stanford.EDU (Fred Gilham)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Process vs Task
Message-ID: <8462@polya.Stanford.EDU>
Date: 14 Apr 89 21:53:10 GMT
References: <8459@polya.Stanford.EDU>
Sender: Fred Gilham <gilham@polya.Stanford.EDU>
Reply-To: gilham@polya.Stanford.EDU (Fred Gilham)
Organization: Stanford University
Lines: 15

In article <8459@polya.Stanford.EDU> rokicki@polya.Stanford.EDU (Tomas G. Rokicki) writes:
>I don't think there is *ever* a reason to use a Task instead of
>a Process---or am I wrong?
>
>-tom
>


With a process you have to fill in some extra blanks.  When I wrote a program
that used two seperate threads of control, I had no reason to give the second
thread any info about working directories, or whatever goes in the process
extension of the task structure.  So why bother?  My understanding is if you
want to make calls to dos, you need to be a process.  Otherwise you can be
a task.  Is this right?
-Fred Gilham