Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!sun-arpa!male!pitstop!texsun!texbell!killer!usl!pcb
From: pcb@usl.usl.edu (Peter C. Bahrs)
Newsgroups: comp.sys.encore
Subject: Threads vs. parallel.h  et.al.
Keywords: stacksize, datasize, threadgo
Message-ID: <795@usl.usl.edu>
Date: 19 Apr 89 04:33:59 GMT
Organization: CACS, Lafayette, LA, USA
Lines: 26

We just finished an object oriented (C++) message passing programming 
environment running under Threads.  
The old version was developed with parallel.h, this one with threads.h.
I still have some questions though...

Is parallel.h et.al. being phased out???  I noticed that including the
two .h files produces a conflict in the Semaphore definition.  Or is
just the task stuff being replace with the threads stuff?

I still am never sure what to set for stack size and datasize in
threadgo and threadcreate.  I am using the constants in the threads.h
file but....

When a threadgo is called, does this create a high priority process that
will not get bumped by the process scheduler?  Also, does this thread scheduler
(the h.pr. process) schedule all thread create objects.  Thread go takes
N as the number of processors to use.  Will jobs remain on the initial
processor that they are scheduled to?

/*------------Thanks in advance...---------------------------------------+
| Peter C. Bahrs                         UUCP ... !uunet!dalsqnt!usl!pcb |
| The USL-NASA Project                        ... !cs.utexas.edu!usl!pcb |
| Center For Advanced Computer Studies   INET  pcb@usl.usl.edu           |
| University of Southwestern Louisiana                                   |
| Lafayette, LA 70504                                                    |
+-----------------------------------------------------------------------*/