CVS difference for ais/ai-10051.txt

Differences between 1.1 and version 1.2
Log of other versions for file ais/ai-10051.txt

--- ais/ai-10051.txt	2004/12/09 18:01:25	1.1
+++ ais/ai-10051.txt	2005/04/13 05:37:24	1.2
@@ -1,4 +1,4 @@
-!standard 13.03    (25)                             04-12-08  AI95-00051-02/01
+!standard 13.03    (25)                             05-04-03  AI95-00051-02/03
 !standard 13.03    (28)
 !standard 13.03    (30)
 !standard 13.03    (31)
@@ -7,7 +7,11 @@
 !standard 13.03    (43)
 !standard 13.03    (50)
 !standard 13.03    (56)
+!standard 13.03    (53)
 !class binding interpretation 95-06-25
+!status Amendment 200Y 05-02-13
+!status WG9 Approved (Letter ballot, 05-01)
+!status ARG Approved 7-0-3  05-02-13
 !status work item 04-12-08
 !status received 04-12-08
 !reference AI95-00291
@@ -78,10 +82,7 @@
 
 Replace 13.3(30-32) with:
 
-    - An implementation should support a confirming Alignment clause for
-      any kind of type.
-
-    - An implementation should support a nonconfirming Alignment clause
+    - An implementation should support an Alignment clause
       for a discrete type, fixed point type, record type, or
       array type, specifying an Alignment value that is zero or
       a power of two, subject to the following:
@@ -99,6 +100,8 @@
       instructions.
 
 Replace 13.3(42-3) with
+    The size of an array object should not include its bounds.
+
     The recommended level of support for the Size attribute of objects is
     the same as for subtypes (see below).
 
@@ -109,11 +112,8 @@
 .
 
 Insert after 13.3(56) (as part of the bulleted list)
-
-    - An implementation should support a confirming Size clause for any
-      kind of type.
 
-    - An implementation should support a nonconfirming Size clause for
+    - An implementation should support a Size clause for
       a discrete type, fixed point type, record type, or array type,
       subject to the following:
 
@@ -133,6 +133,10 @@
   for records need not be the same as the largest size supported for
   arrays.
 
+Replace 13.9(14) with
+  Since the Size of an array object generally does not include its bounds,
+  the bounds should not be part of the converted data.
+
 !discussion
 
 The current recommended level of support, interpreted strictly, includes
@@ -144,6 +148,9 @@
 We "recommend" support for nonconfirming Size and Alignment clauses
 for a discrete and fixed-point type.
 
+A minor fix is to move the advice about the size of array objects from
+13.9 to 13.3, where it actually will be seen by people reading about Size.
+
 !example
 
 This example shows some ramifications of the Recommended Level of Support.
@@ -204,10 +211,7 @@
 and multiples of the number of storage elements per word, subject to the
 following:>
 @dby
-@xbullet<An implementation should support a confirming Alignment clause for
-any kind of type.>
-
-@xbullet<An implementation should support a nonconfirming Alignment clause
+@xbullet<An implementation should support an Alignment clause
 for a discrete type, fixed point type, record type, or
 array type, specifying an Alignment value that is zero or
 a power of two, subject to the following:>
@@ -242,6 +246,8 @@
 @drepl
 The recommended level of support for the Size attribute of objects is:
 @dby
+The size of an array object should not include its bounds.
+
 The recommended level of support for the Size attribute of objects is
 the same as for subtypes (see below).
 
@@ -271,10 +277,7 @@
 @xbullet<For a subtype implemented with levels of indirection, the Size should
 include the size of the pointers, but not the size of what they point at.>
 @dinss
-@xbullet<An implementation should support a confirming Size clause for any
-kind of type.>
-
-@xbullet<An implementation should support a nonconfirming Size clause for
+@xbullet<An implementation should support a Size clause for
 a discrete type, fixed point type, record type, or array type,
 subject to the following:>
 
@@ -285,6 +288,15 @@
 chosen by default). A corresponding limitation may be imposed for
 modular integer types, fixed point types, enumeration types,
 record types, and array types.>
+
+!corrigendum 13.9(14)
+
+@drepl
+The Size of an array object should not include its bounds;
+hence, the bounds should not be part of the converted data.
+@dby
+Since the Size of an array object generally does not include its bounds,
+the bounds should not be part of the converted data.
 
 !ACATS Test
 

Questions? Ask the ACAA Technical Agent