Newsgroups: comp.lang.smalltalk,comp.lang.scheme,comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornell!travelers.mail.cornell.edu!news.kei.com!news.mathworks.com!news.alpha.net!uwm.edu!spool.mu.edu!howland.reston.ans.net!ix.netcom.com!netcom.com!hbaker
From: hbaker@netcom.com (Henry G. Baker)
Subject: Re: Multithreading
Message-ID: <hbakerCz9xzJ.2J9@netcom.com>
Organization: nil
References: <CyyHLD.BIo@world.std.com> <hbakerCyyn4I.8p0@netcom.com> <39trlc$fit@disunms.epfl.ch>
Date: Mon, 14 Nov 1994 20:23:42 GMT
Lines: 25
Xref: glinda.oz.cs.cmu.edu comp.lang.smalltalk:17971 comp.lang.scheme:11271 comp.lang.lisp:15624

In article <39trlc$fit@disunms.epfl.ch> matomira@di.epfl.ch (Fernando Mato Mira) writes:
>In article <hbakerCyyn4I.8p0@netcom.com>, hbaker@netcom.com (Henry G. Baker) writes:
>> 
>> Excuse me, but what makes you think that C++ 'does REAL
>> multithreading'?  The C++ _language_ knows nothing about threads, and
>> therefore you have to take 100% of the responsibility yourself for
>> managing multiple access to shared variables, classes, etc.
>> 
>So? The same is true when you program in threaded C, and this is
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>`real multithreading' in the book of any Unix programmer.
[But it isn't 'real multithreading' by the definition of the original poster.]

You have demonstrated my point quite clearly.

It's clear from a number of posts that people have been flying
propellor planes so long, that they miss the jets that whoosh by them
so fast.  They can't understand why anyone would want to fly anything
but a propellor plane.  Pity....

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


