CVS difference for ais/ai-00272.txt

Differences between 1.3 and version 1.4
Log of other versions for file ais/ai-00272.txt

--- ais/ai-00272.txt	2002/03/13 00:48:28	1.3
+++ ais/ai-00272.txt	2002/05/25 03:42:19	1.4
@@ -1,5 +1,6 @@
-!standard  C.06 (07)                                   02-01-23  AI95-00272/01
+!standard  C.06 (07)                                   02-05-10  AI95-00272/02
 !class binding interpretation 01-09-05
+!status Amendment 200Y 02-05-10
 !status ARG Approved 6-0-0  02-02-12
 !status work item 02-01-23
 !status received 01-08-21
@@ -30,6 +31,7 @@
 type is straightforward, until you realize that "any object" includes a
 slice like X(1..3), which is impossible to access atomically unless the
 machine also has 24-bit instructions, which is unlikely to say the least.
+Is it required to access a slice of an atomic object atomically? (No.)
 
 !recommendation
 
@@ -46,10 +48,10 @@
 
 !discussion
 
-Slices should behave like components for the purposes of atomicity.  That is, a
+Slices should behave like components for the purposes of atomicity. That is, a
 component or slice of an atomic thing is not necessarily atomic.
 
-There is one subtlety associated with parameters.  Consider:
+There is one subtlety associated with parameters. Consider:
 
    type Arr is array (...) of Component;
    pragma Atomic (Arr);
@@ -59,7 +61,7 @@
 If the first subtype, Arr, is unconstrained, then X may designate a slice at
 execution time. So in order to determine if an object is a slice, an
 implementation may need to do some run-time processing. This is unfortunate,
-but then support of pragma Atomic for unconstrained array is problematic
+but then support of pragma Atomic for unconstrained arrays is problematic
 anyway.
 
 Note that in the case where Arr is constrained, passing a (non-trivial) slice

Questions? Ask the ACAA Technical Agent