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-Thread: 103376,229eda63f0d80a47
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,UTF8
Path: 
 g2news1.google.com!news3.google.com!feeder2.cambriumusenet.nl!feed.tweaknews.nl!195.71.90.67.MISMATCH!news.unit0.net!newsfeed01.sul.t-online.de!t-online.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Fri, 05 Nov 2010 12:50:50 +0100
From: Georg Bauhaus <rm-host.bauhaus@maps.futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Q: Profiles
References: <4cd3e506$0$6992$9b4e6d93@newsspool4.arcor-online.net>
 <op.vlo3wkceule2fv@garhos>
In-Reply-To: <op.vlo3wkceule2fv@garhos>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Message-ID: <4cd3ef9a$0$6987$9b4e6d93@newsspool4.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 05 Nov 2010 12:50:50 CET
NNTP-Posting-Host: f994100d.newsspool4.arcor-online.net
X-Trace: 
 DXC=;eU\QmUe:6XU6b:FjPaGjQ4IUK<Cl32<Q4Fo<]lROoRQ8kF<OcfhCO[2@Fg^26\Y6VPCY\c7>ejVX3<ZD[IN]?[X^ee0i3VmWJ\
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:15257
Date: 2010-11-05T12:50:50+01:00
List-Id: <comp.lang.ada>

On 11/5/10 12:37 PM, Yannick Duchêne (Hibou57) wrote:
> Le Fri, 05 Nov 2010 12:05:42 +0100, Georg Bauhaus <rm-host.bauhaus@maps.futureapps.de> a écrit:
>
>> The Ravenscar profile (and the Restricted profile in GNAT)
>> assume we want our tasks to run forever. Programs will be
>> supported by a lean and efficient run-time.
>>
>> What if I just want the lean and efficient Ravenscar run-time
>> but do want my tasks to terminate?
> What is the impact of using a system designed to run for ever for an application which is expected to run short or not very long ?

Part of the system (run-time system?) is that it is lean
and efficient.

Assume programs tat are designed to run for a few days.
Their communication structure is easily expressed
since  the tasks communicate along very few lines.

No fancy tasking things (Ravenscar is on).

Basically, the tasks express independent sequences of
statement whose results is to be coordinated every once
in a while, and when they have finished.