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.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM, FROM_STARTS_WITH_NUMS autolearn=no autolearn_force=no version=3.4.4 X-Received: by 10.107.84.8 with SMTP id i8mr13475026iob.66.1520332290241; Tue, 06 Mar 2018 02:31:30 -0800 (PST) X-Received: by 10.157.41.184 with SMTP id n53mr947515otb.11.1520332290035; Tue, 06 Mar 2018 02:31:30 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.unit0.net!peer01.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!e10no1700680itf.0!news-out.google.com!a2ni4241ite.0!nntp.google.com!e10no1700679itf.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 6 Mar 2018 02:31:29 -0800 (PST) In-Reply-To: <90838aa0-bd51-4913-b0cf-1ded5024c151@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=85.240.217.2; posting-account=rhqvKAoAAABpikMmPHJSZh4400BboHwT NNTP-Posting-Host: 85.240.217.2 References: <90838aa0-bd51-4913-b0cf-1ded5024c151@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: multiple delay alternative From: Mehdi Saada <00120260a@gmail.com> Injection-Date: Tue, 06 Mar 2018 10:31:30 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Body-CRC: 2883041985 X-Received-Bytes: 2272 Xref: reader02.eternal-september.org comp.lang.ada:50832 Date: 2018-03-06T02:31:29-08:00 List-Id: > If a protected function call is active, all waiting function calls (again= parameters evaluated immediately) Ok, I got this. Simultaneous, but blocked by use of protected procedures an= d entries. > For subprograms of a protected object, the call is evaluated immediately,= even if the protected object is busy. Then procedure calls are executed = sequentially Still don't get it, sorry... What's the difference *as far as waiting to be= served one after the other* ? I know, there's no guard, and the only thing that matter is if a procedure = or entry is active at the same time. Ok. Then what... the caller tasks are = still waiting to execute the procedure, one after the other, and before the= y are blocked... Just like with an entry ?? You see where I'm stucked ? Oth= er subtleties don't concern me for now. I must get the essential difference= in behavior first. Maybe a drawing or an actual example would do the trick ;-) Sorry, I feel l= ike I'm not always that smart :-)