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=unavailable autolearn_force=no version=3.4.4 Path: buffer2.nntp.dca1.giganews.com!border2.nntp.dca1.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!newspeer1.nac.net!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!news.stack.nl!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: "J-P. Rosen" Newsgroups: comp.lang.ada Subject: Re: Timeouts in Ada Date: Thu, 17 Jul 2014 12:00:38 +0200 Organization: A noiseless patient Spider Message-ID: References: <50bdb713-7ce1-411b-810b-9bdee1d26b7a@googlegroups.com> <13ac2779-31e2-4ee9-879a-826335d2ae7d@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Injection-Date: Thu, 17 Jul 2014 10:00:37 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="23dab0694e4174fdc880833ec67fa650"; logging-data="20060"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+GLV42G9YTzcwy5FYl3ce7" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 In-Reply-To: <13ac2779-31e2-4ee9-879a-826335d2ae7d@googlegroups.com> Cancel-Lock: sha1:clT0xZXwYHWbGtdFwczCOmBioaU= X-Enigmail-Version: 1.6 Xref: number.nntp.dca.giganews.com comp.lang.ada:187646 Date: 2014-07-17T12:00:38+02:00 List-Id: Le 17/07/2014 10:40, NiGHTS a écrit : > I was mainly confused by the fact that the delay command was placed > inside the body of a fork in the path of logic, making it seem as > though in order to satisfy the syntax it had to do things > concurrently. ARM seems to imply that it expects a delay in the body > (first command?) as a condition to determine which path to take. I'm > still a little fuzzy on the mechanics but I'm sure this will clear up > as I do some more reading on the C variant. > Hmmm... The intent is clearer if you write it this way: select or delay 10.0; end select; But be aware NOT to try to understand the rendezvous in terms of mutexes, conditional variables, and the like; it is a much higher level communication mechanism. It's really a client exchanging data synchronously with a server. To me, mutexes are to concurrency what gotos are to sequential programming: a low level tool which is best hidden behind higher level constructs. -- J-P. Rosen Adalog 2 rue du Docteur Lombard, 92441 Issy-les-Moulineaux CEDEX Tel: +33 1 45 29 21 52, Fax: +33 1 45 29 25 00 http://www.adalog.fr