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-Thread: 103376,7b6ebbd3cbca32ce X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!feeder.news-service.com!newsfeeder.dynfx.net!weretis.net!news-peer.in.tum.de!lrz.de!not-for-mail From: Sebastian Hanigk Newsgroups: comp.lang.ada Subject: Re: run tasks on events Date: Thu, 29 May 2008 12:31:40 +0200 Organization: [posted via] Leibniz-Rechenzentrum, Muenchen (Germany) Message-ID: References: NNTP-Posting-Host: kelvin.fs.tum.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.lrz-muenchen.de 1212057100 13213 129.187.202.43 (29 May 2008 10:31:40 GMT) X-Complaints-To: newsmaster@lrz-muenchen.de NNTP-Posting-Date: Thu, 29 May 2008 10:31:40 +0000 (UTC) Mail-Copies-To: never User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (darwin) Xref: g2news1.google.com comp.lang.ada:447 Date: 2008-05-29T12:31:40+02:00 List-Id: ahab writes: > Have the task immediately call a suspension object or a protected > entry. Hmm, this works only for one task if I'm not mistaken (a suspension object allows only one blocking call to Suspend_Until_True at the same time, a protected entry seems to have similar constraints). A solution would be a suspension object per task, but this is far from the elegance of HAL/S' signals. Sebastian