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,LOTS_OF_MONEY autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,77efb4ab26922e3 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!club-internet.fr!feedme-small.clubint.net!nuzba.szn.dk!news.jacob-sparre.dk!pnx.dk!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Blocking syscalls in Tasks Date: Mon, 29 Sep 2008 21:35:52 -0500 Organization: Jacob's private Usenet server Message-ID: References: NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: jacob-sparre.dk 1222742188 14973 69.95.181.76 (30 Sep 2008 02:36:28 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Tue, 30 Sep 2008 02:36:28 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5512 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Xref: g2news1.google.com comp.lang.ada:2149 Date: 2008-09-29T21:35:52-05:00 List-Id: Probably because for Janus/Ada, pretty much everything you said about the mapping of Ada tasks to threads is wrong. Janus/Ada still maps all tasks to one Windows thread. That was originally supposed to be a temporary Q&D implementation, but for a variety of reasons it never got replaced. Most obviously: other things needed work more urgently than the tasking, which is quite efficient. Depending on your circumstances, it might actually be faster than a threaded implementation. (Our ultimate goal is to have both.) In any case, the point is that Ada doesn't say anything about the mapping of tasks to OS threads: you simply have to ask your vendor. And, of course blocking of system calls follows from that. Randy. "anon" wrote in message news:eBUDk.245076$102.150485@bgtnsc05-news.ops.worldnet.att.net... > Each and every time you speak you CUT the post down Ada! > WHY are you trying to KILL Ada! And I say nothing that is > confusing except to those who hate Ada. > > An event thread is a blocked thread. See Microsoft Windows Documentation! > LEARN before speaking! > > In , tmoran@acm.org writes: >>> Except for DOS in todays OS all Ada partitions are executed by native OS >>> threads. >> This is confusing. An Ada partition is not at all the same as an Ada >>task, and there's no guarantee that an Ada task maps 1-1 to an OS thread. >> >>> Now, in a GUI system, the RC_TASK (resource task) is blocked until a >>> input >>> device such as the mouse or keyboard actives the thread. >> MS Windows tasks do not block waiting for mouse or keyboard. Windows >>"event based" GUI design was based on a single thread and a polling loop. >