From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: *
X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_20,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Xref: utzoo comp.edu:2879 comp.lang.ada:3143 comp.lang.misc:3850
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uwm.edu!uakari.primate.wisc.edu!ames!ncar!boulder!agcsun!marks
From: marks@agcsun.UUCP (Mark Shepherd)
Newsgroups: comp.edu,comp.lang.ada,comp.lang.misc
Subject: Re: Teaching Concurrency
Summary: dangers of toy tasking assignment
Message-ID: <602@agcsun.UUCP>
Date: 10 Jan 90 20:49:54 GMT
References: <7588@hubcap.clemson.edu>
Organization: Ampex VSD Golden Engineering, Golden, CO
List-Id: <comp.lang.ada>

In article <7588@hubcap.clemson.edu>, wtwolfe@hubcap.clemson.edu (Bill Wolfe) 
posts some excerpts from an article on the teaching of concurrency
in ACM SIGAda Ada Letters. The article discusses programming assignments
where concurrent tasks are used for things like sorting numbers, solving 
equations, finding primes, etc.

Although these programming assignments evidently had some valuable lessons
on multi-tasking, I feel that they may also inadventantly teach a
less desirable lesson: that it is OK to use concurrent tasks for things 
that could be done much more simply with subroutines. 

In real life (whether industrial, business, scientific research, or whatever),
multi-tasking applications carry substantial penalties
in complexity and resource utilization, and should only be used when
appropriate. (Of course, NOT using tasking when it should be used has  
equally dire consequences). 

I have seen large (and expensive!) systems crippled by inappropriate use
of tasking, and I hope the the computer science graduates of the future
will understand not only HOW to use multi-tasking, but WHEN.

Mark Shepherd
agcsun!marks@boulder.colorado.edu