Newsgroups: comp.lang.smalltalk,comp.lang.scheme,comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!nntp.club.cc.cmu.edu!hudson.lm.com!news.pop.psu.edu!news.cac.psu.edu!howland.reston.ans.net!ix.netcom.com!netcom.com!hbaker
From: hbaker@netcom.com (Henry G. Baker)
Subject: Re: Multithreading
Message-ID: <hbakerCz44Jp.H8y@netcom.com>
Organization: nil
References: <CyyHLD.BIo@world.std.com> <hbakerCyyn4I.8p0@netcom.com> <GWYANT.94Nov10133254@cloyd.east.sun.com>
Date: Fri, 11 Nov 1994 16:59:48 GMT
Lines: 24
Xref: glinda.oz.cs.cmu.edu comp.lang.smalltalk:17884 comp.lang.scheme:11167 comp.lang.lisp:15584

In article <GWYANT.94Nov10133254@cloyd.east.sun.com> gwyant@cloyd.east.sun.com (Geoffrey Wyant - Sun Microsystems Labs BOS) writes:
>Just to add fuel to the fire, the Modula-3 programming language has 
>supported threads since the beginning. There is a freely available,
>high-quality implementation available (native compiler on most 
>Unix platforms w/ NT&Windows-95 in the works, incremental/
>generational/conservative GC, minimal recompilation, distributed objects)
>in source form via anonymous FTP: ftp://gatekeeper.dec.com/pub/DEC/Modula-3.
>The threads in this system do the right thing with respect to IO - when one
>thread blocks on IO, another thread is scheduled.
>
>Anyone interested in high-quality next-generation systems/applications 
>languages should take a hard look at Modula-3 and the DEC Systems Research
>Center implementation mentioned above !

This is all pretty interesting, since I have been told that the most
obvious example of an Ada which _doesn't_ do threads correctly with
respect to I/O is _DEC_ VAX Ada.  Either they learned from their Ada
experience or they sand-bagged the Ada product to make Modula look
good.

      Henry Baker
      Read ftp.netcom.com:/pub/hbaker/README for info on ftp-able papers.
      Contact hoodr@netcom.com if you have trouble ftping

