Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!m.cs.uiuc.edu!schwager
From: schwager@m.cs.uiuc.edu (Michael Schwager)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: "Task"'ing trubbles
Message-ID: <1991May24.152809.29687@m.cs.uiuc.edu>
Date: 24 May 91 15:28:09 GMT
References: <1991May21.063012.1358@m.cs.uiuc.edu> <fjrei.9418@kbsaar.UUCP>
Organization: University of Illinois, Dept. of Comp. Sci., Urbana, IL
Lines: 16

fjrei@kbsaar.UUCP (Franz-Josef Reichert) writes:

>In article <1991May21.063012.1358@m.cs.uiuc.edu> schwager@m.cs.uiuc.edu (Michael Schwager) writes:
>>So, it doesn't work.  My main program calls the function "flash" that
>>creates the Task "flashTask".  The Task "flashTask" calls another function
>>named "myDelay"... it works just like DOS' Delay() but using timer.device.

>Who is setting up the MsgPort/timerequest for your timer.device stuff?
>As I see, flashTask() didn't! So the mp_SigTask may be wrong (i.e.
>contain the address of the parent task's control block), which will cause
>flashTask() waiting forever for a signal which never occures.  

Ahhh!  Thanks!  I had figured out that it was waiting forever in myDelay(),
but I didn't quite understand why.  Now I get it!  Indeed, using AskTask
showed that my new task was waiting for a signal.  Thanks muchly.
-Mike