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,a023f5759065182 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-11-28 23:02:57 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed.icl.net!newsfeed.fjserv.net!news.mailgate.org!newsfeed.wirehub.nl!kleenex.wirehub.nl!newsf01.ono.com!news.ono.com.POSTED!not-for-mail From: "Ivan" Newsgroups: comp.lang.ada References: Subject: Re: Selective accept in Ada tasking X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4920.2300 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300 Message-ID: Date: Fri, 29 Nov 2002 07:02:51 GMT NNTP-Posting-Host: 62.42.227.26 X-Complaints-To: abuse@ono.com X-Trace: news.ono.com 1038553371 62.42.227.26 (Fri, 29 Nov 2002 08:02:51 MET) NNTP-Posting-Date: Fri, 29 Nov 2002 08:02:51 MET Xref: archiver1.google.com comp.lang.ada:31306 Date: 2002-11-29T07:02:51+00:00 List-Id: I have analyze all my code and make some tests and I was confused. The problem with the CPU wasn't in the selective accept. It seems to be OK. We can have a task with a infinte loop and a selective accept with the "or terminate" clause without making our CPU burn ;-). Thank you for your time and sorry.