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: 
 eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!feeder.erje.net!1.eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Niklas Holsti <niklas.holsti@tidorum.invalid>
Newsgroups: comp.lang.ada
Subject: Re: Ravenscar References
Date: Tue, 29 Jan 2019 21:24:21 +0200
Organization: Tidorum Ltd
Message-ID: <gbbnj1F65bbU1@mid.individual.net>
References: <q1nqpc$f2k$1@gioia.aioe.org> <q1p3vl$gbn$1@dont-email.me>
 <87f58059-72c9-4416-a24f-0251f6bceffd@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net FaisRDsvQ9iH7qaP0uODXgdSduYGsnqLOegHUdU24OgbbwzNFl
Cancel-Lock: sha1:Cfu35cNsGmUTQqneNScVw/Zj4rQ=
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:45.0)
 Gecko/20100101 Thunderbird/45.8.0
In-Reply-To: <87f58059-72c9-4416-a24f-0251f6bceffd@googlegroups.com>
Xref: reader01.eternal-september.org comp.lang.ada:55402
Date: 2019-01-29T21:24:21+02:00
List-Id: <comp.lang.ada>

On 19-01-29 03:08 , Jorge Real wrote:
> El jueves, 17 de enero de 2019, 6:31:34 (UTC+1), J-P. Rosen  escribió:
>> Le 16/01/2019 à 18:48, lyttlec a écrit :
>>> Can anyone suggest a good reference on using the ravenscar profile? In
>>> the Ada books I have, it only gets a one or two page mention. A
>>> reference with an extended case study would be great.
>>>
>> Did you get the official report at
>> http://www.open-std.org/jtc1/sc22/wg9/n424.pdf
>> ?
>
> Note there is a revised version of of the Ravenscar guide at
> http://www.open-std.org/JTC1/SC22/WG9/n575.pdf
>
> This version of June 2017 is adapted to Ada 2012 TC1.

But, disappointingly, it still contains the (IMO) misleading advice that 
"All global objects that are either of a protected type or an atomic 
type may be safely shared".

IMO atomic-type objects can be safely shared only if care is taken to 
follow a proper lock-free read/write protocol.

-- 
Niklas Holsti
Tidorum Ltd
niklas holsti tidorum fi
       .      @       .