comp.lang.ada
 help / color / mirror / Atom feed
From: Niklas Holsti <niklas.holsti@tidorum.invalid>
Subject: Re: Ravenscar References
Date: Tue, 29 Jan 2019 21:24:21 +0200
Date: 2019-01-29T21:24:21+02:00	[thread overview]
Message-ID: <gbbnj1F65bbU1@mid.individual.net> (raw)
In-Reply-To: <87f58059-72c9-4416-a24f-0251f6bceffd@googlegroups.com>

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
       .      @       .

  reply	other threads:[~2019-01-29 19:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 17:48 Ravenscar References lyttlec
2019-01-16 18:15 ` Simon Wright
2019-01-18 19:18   ` lyttlec
2019-01-20 17:12     ` Jeffrey R. Carter
2019-01-21 23:19       ` Randy Brukardt
2019-01-22  9:25         ` J-P. Rosen
2019-01-22 22:05           ` Randy Brukardt
2019-01-28  0:38             ` lyttlec
2019-01-17  5:31 ` J-P. Rosen
2019-01-17  8:46   ` Niklas Holsti
2019-01-29  1:08   ` Jorge Real
2019-01-29 19:24     ` Niklas Holsti [this message]
2019-02-01 10:06       ` Jorge Real
2019-02-02  2:13       ` Jere
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox