CVS difference for ai05s/ai05-0193-1.txt

--- ai05s/ai05-0193-1.txt	2010/01/09 01:31:30	1.5
+++ ai05s/ai05-0193-1.txt	2010/06/07 18:20:28	1.6
@@ -1,4 +1,4 @@
-!standard  13.11(16/2)                                  09-11-30  AI05-0193-1/02
+!standard  13.11(16)                                  10-06-06  AI05-0193-1/03
 !standard  13.11(21)
 !standard  13.11.1 (0)
 !standard  13.11.1 (1)
@@ -16,7 +16,8 @@
 
 !summary
 
-Implementations may request more strictly aligned data for allocators.
+Ada implementations may request more strictly aligned data for allocators. In
+addition, the attribute Max_Alignment_For_Allocation is added.
 
 !problem
 
@@ -24,7 +25,7 @@
 RM 13.11(16) completely specifies the value of the Alignment parameter passed in
 the associated call to Allocate.
 
-This may be inappropriate in some cases. If an implementation chooses to
+This may be inappropriate in some cases. If an Ada implementation chooses to
 allocate space for additional (typically contiguous) data, the alignment
 requirements of this additional data may be stricter than the specified
 Alignment value. In this case, the implementation should have the freedom to
@@ -58,7 +59,7 @@
 stricter alignment requirement than that of the access-discriminant-bearing
 "owner" type.
 
-The Max_Size_In_Storage_Units attribute was designed to cope with all of these
+The Max_Size_In_Storage_Elements attribute was designed to cope with all of these
 issues as they relate to the value of the Size_In_Storage_Elements parameter
 value that is passed to Allocate. An analogous attribute is needed for the
 Alignment parameter.
@@ -70,7 +71,7 @@
 !wording
 
 In the Implementation Requirements added by AI05-0107-1 (which replaces
-paragraph 13.11(16/2)), replace
+paragraph 13.11(16)), replace
      The Alignment parameter is D'Alignment if D is a specific type,
      and otherwise is the alignment of the specific type identified by
      the tag of the object being created.
@@ -84,7 +85,7 @@
 
      13.11.1 Storage Allocation Attributes
 
-     The Max_Size_In_Storage_Units and Max_Alignment_For_Allocation
+     The Max_Size_In_Storage_Elements and Max_Alignment_For_Allocation
      attributes may be useful in writing user-defined pool types.
 
      Static Semantics
@@ -190,19 +191,19 @@
 implementation allocates space for a coextension in the same pool as
 that of the object having the access discriminant, then this accounts
 for any calls on Allocate that could be performed to provide space for
-such coextensions. The value of this attribute is of type universal_integer.>
+such coextensions. The value of this attribute is of type @i<universal_integer>.>
 @dby
 @xhang<@xterm<S'Max_Size_In_Storage_Elements>
 Denotes the maximum value for Size_In_Storage_Elements that could be
 requested by the implementation via Allocate for an access type whose
 designated subtype is S. The value of this attribute is of type
-universal_integer.
+@i<universal_integer>.
 
 @xhang<@xterm<S'Max_Alignment_For_Allocation>
 Denotes the maximum value for Alignment that could be requested
 by the implementation via Allocate for an access type whose
 designated subtype is S. The value of this attribute is of type
-universal_integer.>
+@i<universal_integer>.>
 
 For a type with access discriminants, if the implementation 
 allocates space for a coextension in the same pool as that of the