Excerpted from message dated 02-07-96, David Noon to Murray Lesser:

DN>I think attaching and detaching tasks/threads should be viewed like
  >opening and closing files: any file your routine opens, it should
  >close; any thread your routine attaches it should stop/wait and
  >detach.

DN>It is also a requirement to be portable to MVS...

DN>And by observing the MVS rules, people writing code under OS/2 will
  >not only have portable code but avoid memory (and other resource)
  >leaks too.

Hi David--

    Thank you for the exposition on multithreading.  I would imagine
that its message is also excellent advice for other multithreading
neophytes in this echo who are so benighted as to use a programming
language that doesn't include multithreading as part of the language
definition .

    Heaven help any of my programs recompiled for the big iron!  My
"Personal Edition" of the PL/I compiler can't speak EBCDIC!  Now I know
why UNSPEC() is so dangerous!

    Inflationary note:  A year or so ago, when I started to learn PL/I
under your tutelage, I bought a copy of the third edition (1986 vintage)
of Joan Hughes' book on PL/I programming from my local bookseller (since
closed due to the impact of the big discount chains).  The book cost me
$55.85.  Yesterday, I was in the Poughkeepsie branch of Barnes & Noble
(one of those big discount chains).  There was a copy of the book on the
"advanced programming" shelf, marked $68.50!

    Regards,

          --Murray

___
 * MR/2 2.26 * Fidonet is almost like having a social life
                                                                           
                               
---