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,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,385c146dd3112519
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news1.google.com!postnews.google.com!q16g2000yqq.googlegroups.com!not-for-mail
From: =?ISO-8859-1?Q?Hibou57_=28Yannick_Duch=EAne=29?=
 <yannick_duchene@yahoo.fr>
Newsgroups: comp.lang.ada
Subject: Re: Private or public task ?
Date: Tue, 9 Feb 2010 10:17:55 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <b28678e3-d25e-437c-bb63-856c90c90e9d@q16g2000yqq.googlegroups.com>
References: 
 <a35584dd-8693-484d-918d-758940dccfe8@d37g2000yqa.googlegroups.com>
	<hki3p7$bas$1@tornado.tornevall.net>
 <38a0a3f9-b4a0-48f3-98c9-63b03fe03aca@q4g2000yqm.googlegroups.com>
	<e714f043-9fed-4e2b-b3d2-180b0364f0cf@d27g2000yqn.googlegroups.com>
	<f7048897-bce0-4e1d-8f49-85fe274d7292@v25g2000yqk.googlegroups.com>
	<narrkh.9g.ln@hunter.axlog.fr>
NNTP-Posting-Host: 79.91.74.81
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1265739475 11432 127.0.0.1 (9 Feb 2010 18:17:55
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 9 Feb 2010 18:17:55 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: q16g2000yqq.googlegroups.com; posting-host=79.91.74.81;
	posting-account=vrfdLAoAAAAauX_3XwyXEwXCWN3A1l8D
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
	fr),gzip(gfe),gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:9043
Date: 2010-02-09T10:17:55-08:00
List-Id: <comp.lang.ada>

On 9 f=E9v, 15:26, Jean-Pierre Rosen <ro...@adalog.fr> wrote:
> protected procedures are bounded, because if you know the processing
> time and the maximum number of tasks waiting, you know the WCET of the
> procedure. Entries are unbounded, because they depend on a guard whose
> condition can be anything.
>
> The "potentially blocking" phrase should be understood as really meaning
> unbounded. =A0This all boils down to: "an operation with a bounded
> execution time is not allowed to call an operation with an unbounded
> execution time".
>
> Makes more sense?
Yes, more sense. Bounded/Unbounded execution-time is better
expressive.


Side note. For peoples who like me didn't knew what is WCET : its
"Worst Case Execution Time" (dixit Wikipedia).