CVS difference for ais/ai-00181.txt

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

--- ais/ai-00181.txt	1998/09/30 00:17:33	1.1
+++ ais/ai-00181.txt	1999/06/26 01:11:13	1.2
@@ -1,5 +1,6 @@
-!standard 13.13.01 (04)                               97-11-14  AI95-00181/02
+!standard 13.13.01 (04)                               99-06-25  AI95-00181/03
 !class binding interpretation 97-03-19
+!status Corrigendum 2000 99-05-27
 !status WG9 Approved  97-11-14
 !status ARG Approved (letter ballot: 9-1-1)  97-10-27
 !status ARG Approved (subject to letter ballot) 8-1-1  97-04-11
@@ -7,9 +8,9 @@
 !status received 97-03-19
 !priority High
 !difficulty Easy
-!subject components of Stream_Element_Array should be ALIASED
+!subject components of Stream_Element_Array should be Aliased
 
-!summary 97-05-08
+!summary
 
 The components of Streams.Stream_Element_Array are aliased:
 
@@ -22,21 +23,21 @@
 If Stream_Element'Size is not a multiple of System.Storage_Unit,
 then the components of Stream_Element_Array need not be aliased.
 
-!question 97-05-08
+!question
 
 13.13.1(4) does not define the components of
 Streams.Stream_Element_Array to be aliased.  However, this makes various
 uses of this type inconvenient.  What is the intent?
 
-!recommendation 97-05-08
+!recommendation
 
 On machines where it is feasible, the components should be aliased.
 
-!wording 97-03-19
+!wording
 
 (See Summary.)
 
-!discussion 97-05-08
+!discussion
 
 On machines where it is feasible, one should be allowed to form access
 values pointing to any component within a Stream_Element_Array.
@@ -45,9 +46,37 @@
 the "network".  Therefore, the requirement to be aliased is relaxed on
 such machines.  Programmers wishing to write code that is portable to
 such machines should not take advantage of the aliased components.
+
+!corrigendum 13.13.01(4)
+
+@dprepl
+@xcode<
+@b<type> Stream_Element_Array @b<is>
+    @b<array>(Stream_Element_Offset @b<range> <@>) @b<of> Stream_Element;>
+@dby
+@xcode<
+@b<type> Stream_Element_Array @b<is>
+    @b<array>(Stream_Element_Offset @b<range> <@>) @b<of aliased> Stream_Element;>
+
+!corrigendum 13.13.01(9)
+
+@dinsa
+The Write operation appends Item to the specified stream.
+@dinst
+@i<@s8<Implementation Permissions>>
+
+If Stream_Element'Size is not a multiple of System.Storage_Unit,
+then the components of Stream_Element_Array need not be aliased.
+
+!ACATS test
 
-!appendix 97-10-27
+A C-Test should be created to check that the components are aliased. There
+should be applicability criteria allowing the test to be rejected (similarly
+to the representation clause tests), and marked Not Applicable for an
+implementation taking advantage of the implementation permission.
 
+!appendix
+
 !section 13.13.1(00)
 !subject components of Stream_Element_Array should be ALIASED
 !reference RM95-13.13.1
@@ -56,7 +85,7 @@
 !discussion
 
 The word "aliased" should be added to the declaration of type
-Stream_Element array.  
+Stream_Element array.
 
 The intended use of this type is for buffers.  When one attempts
 to use this type for that purpose, one finds it necessary to pass
@@ -95,7 +124,7 @@
 !discussion
 
 > The word "aliased" should be added to the declaration of type
-> Stream_Element array.  
+> Stream_Element array.
 
 There is no requirement that a Stream_Element be as big as
 a Storage_Element.  In fact, it was anticipated that
@@ -179,13 +208,13 @@
 !discussion
 
 > Tucker Taft said:
-> 
+>
 > | There is no requirement that a Stream_Element be as big as
 > | a Storage_Element.  In fact, it was anticipated that
 > | on word-addressible machines with word sizes such as 24 bits or
 > | 36 bits, Stream_Elements would still be 8 or 9 bits, representing
 > | the unit of I/O, rather than the unit of addressibility.
-> 
+>
 > Such machines are rather rare.  Could we not at least give a
 > recommendation (or at least permission) for an implementation to
 > add "aliased" to this array type declaration if Stream_Element's
@@ -251,7 +280,7 @@
 operations are defined as follows:
 
    subtype IO_Buffer is POSIX.POSIX_String;
-   procedure Read                          
+   procedure Read
       (File:           in  File_Descriptor;
        Buffer:         out IO_Buffer;
        Last:           out POSIX.IO_Count;
@@ -327,7 +356,7 @@
 !discussion
 
 >> The word "aliased" should be added to the declaration of type
->> Stream_Element array.  
+>> Stream_Element array.
 >
 >There is no requirement that a Stream_Element be as big as
 >a Storage_Element.  In fact, it was anticipated that

Questions? Ask the ACAA Technical Agent