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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,fca4fc92ad494c1f,start
X-Google-Attributes: gid103376,public
From: paulvg@eelab.su.oz.au (Paul Van Gorp)
Subject: Tasking question (not the same as ^^^)
Date: 1997/10/10
Message-ID: <61kipb$p28$1@reader1.reader.news.ozemail.net>#1/1
X-Deja-AN: 279135454
X-Complaints-To: abuse@ozemail.com.au
X-Trace: reader1.reader.news.ozemail.net 876465771 25672 (None) 203.22.157.28
Organization: n/a
Newsgroups: comp.lang.ada
Date: 1997-10-10T00:00:00+00:00
List-Id: <comp.lang.ada>


I am having this strange problem with tasking, here is the scenario...

task DO_STUFF is
	entry do_stuff1(...);
	entry do_stuff2(...);
end DO_STUFF;

task user is	-- interacts with DO_STUFF
	entry input_entered(c: Character);	-- the body for this interacts with DO_STUFF
end user;

-- and the mail program has this loop...

begin 

...
	loop
		ch := Getch;	-- doesn't have to be Getch, could just be a read
		user.input_entered(ch);
	end loop
...
end ...;

Now, It may be a rotten way to do it, but it works fine when there is no
facility for a simple keyboard interface, the tasks all seem to not operate
when input is being awaited from the keyboard.

It seems to work fine when I hardcode input ( user.input_entered(...) ) in the
main part of the program.

Wondering if anyone might have a clue as to what the program might be...

Thanks in advance..

Paul