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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5400c39557b9f344 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-12-09 02:44:35 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!logbridge.uoregon.edu!newsfeed.vmunix.org!feed.news.nacamar.de!news.belwue.de!contact.softwarezentrum.de!news.bawue.de!lemmies.lb.bawue.de!not-for-mail From: lemchens@lemmies.lb.bawue.de (arvids lemchens) Newsgroups: comp.lang.ada Subject: Re: Multitasking Date: 09 Dec 2002 10:57:00 +0100 Organization: A poorly-maintained Debian GNU/Linux InterNetNews site Sender: news@pd90183c4.dip.t-dialin.net Message-ID: <8bW1jK0+ACB@lemmies.lb.bawue.de> References: <8bRwOT7FACB@lemmies.lb.bawue.de> NNTP-Posting-Host: pd90183c4.dip.t-dialin.net X-Trace: pc4.dv-lemchens.de 1039427858 1476 192.168.2.6 (9 Dec 2002 09:57:38 GMT) User-Agent: OpenXP/32 v3.8.7pl1 (Linux) beta @ 2002-08-04-1336f Xref: archiver1.google.com comp.lang.ada:31576 Date: 2002-12-09T10:57:00+01:00 List-Id: Hello Micha, vinnie@inetia.pl am 07.12.02 um 15:10 in comp.lang.ada: >> Now i am wondering why the maintask is waiting for the completion of >> S and T and not going independent of them on? > Entry is a synchronization mechanism. That means that it is used to > synchronize two tasks with each other. The caller (in your code the > main task) will not return until the entry is finished. Ok, know i am understanding. >> Am i missing something fundamental about ada-tasks? > It looks that you do (don't take this as offence :-)) I know, but now it's better. ... i hope so >> If yes, what and how do i get them running independent? > You did it. But what do you want to achieve with your code? I was thinking about a monitoring application, where the monitored items would be monitored by different tasks and the main task only runs in a loop, triggering the tasks and getting the results. So i stumbled on this issue. Seems to be a better approach, to split the triggering/ monitoring and the resultholding in two different tasks. MvfG, Arvids