Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cbmvax!valentin
From: valentin@cbmvax.commodore.com (Valentin Pepelea)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Task Switching Problem
Message-ID: <14782@cbmvax.commodore.com>
Date: 2 Oct 90 02:13:13 GMT
References: <1990Sep21.180100.28580@uncecs.edu> <14593@cbmvax.commodore.com>
Reply-To: valentin@cbmvax.commodore.com (Valentin Pepelea)
Organization: Commodore, West Chester, PA
Lines: 23

In article <1990Sep27.141415.29158@uncecs.edu> utoddl@uncecs.edu (Todd M.
Lewis) writes:
>
> Ok, I can buy that.  I'll try this instead--I'll make two tasks which
> signal each other and wait on each other's signals.  One of these will do
> the monitoring I want to have, while the other will be there simply
> to wake up the first task each time the robin goes 'round.  It isn't
> quite as efficient as I had planned, but what I want to test is 
> task-relative anyway, not real-time sensitive.  Any problems with this?

Yes. You're missing the point. Signal/Wait are for synchronizing on event
occurances. The round-robin loop around is not an appropriate event to
synchronize on.

Tell me what you want to do, and I'll show you the proper method/algorithm
to do it.

Valentin
-- 
The Goddess of democracy? "The tyrants    Name:    Valentin Pepelea
may destroy a statue,  but they cannot    Phone:   (215) 431-9327
kill a god."                              UseNet:  cbmvax!valentin@uunet.uu.net
             - Ancient Chinese Proverb    Claimer: I not Commodore spokesman be