CVS difference for ais/ai-00283.txt

Differences between 1.10 and version 1.11
Log of other versions for file ais/ai-00283.txt

--- ais/ai-00283.txt	2003/03/04 04:59:45	1.10
+++ ais/ai-00283.txt	2003/05/24 00:51:38	1.11
@@ -1,4 +1,4 @@
-!standard A.12.01    (28)                               03-02-18  AI95-00283/02
+!standard A.12.01    (28)                               03-05-03  AI95-00283/03
 !standard A.08.02    (03)
 !standard A.08.02    (10)
 !standard A.08.02    (16)
@@ -8,7 +8,7 @@
 !status ARG Approved 5-0-3  03-02-09
 !status work item 02-06-10
 !status received 01-12-14
-!qualifier Clarification
+!qualifier Error
 !priority Low
 !difficulty Medium
 !subject Truncation of stream files by Close and Reset
@@ -28,7 +28,7 @@
 !recommendation
 
 Stream_IO files are not sequential files, and are not truncated on Close
-and Reset as described in A.8.2(10) and A.8.2(16).
+and Reset as described for sequential files in A.8.2(10) and A.8.2(16).
 
 !wording
 
@@ -48,8 +48,9 @@
    * If positioning is supported for the given external file, the function
      returns True if the current index exceeds the size of the external file;
      otherwise it returns False;
-   * Otherwise, the function returns True if no more elements can be read from
-     the given file; otherwise it returns False.
+   * If positioning is not supported for the given external file, the function
+     returns True if no more elements can be read from the given file;
+     otherwise it returns False.
 
 !discussion
 
@@ -63,11 +64,12 @@
 set of operations should remain intact. Thus, the behavior of these compilers
 is incorrect.
 
-We considered requiring truncation as described in the RM. However, this
+We considered requiring truncation as described in the standard. However, this
 is expensive on Unix systems (which do not have a truncate file operation),
 and no compiler currently implements it. Moreover, this is not particularly
-useful functionality. The behavior of existing compilers is easily
-accomplished by a Delete followed by Create sequence.
+useful functionality. When it is needed, the behavior of existing compilers is
+easily accomplished by a Delete followed by Create sequence, so a rule like
+the existing one is not necessary.
 
 The AARM indicates that stream files are not sequential files. This implies
 that behavior specific to sequential files (such as truncation) is not
@@ -76,7 +78,7 @@
 define "stream file" as a term. And the equivalence in A.12.1(28) specifies
 "Sequential_IO", so arguably the behavior of sequential files applies.
 
-Thus we correct the oversight of defining the term "stream file", and we
+Thus we correct the oversight by defining the term "stream file", and we
 remove the reference to Sequential_IO from the specification of these
 routines. The wording used is similar to that used in the definition of
 Text_IO (A.10.2(1)). Having done so, the specific requirements in A.8.2 no
@@ -87,7 +89,7 @@
 Finally, we define the behavior of End_of_File directly in A.12.1. Since stream
 files can be positioned, the equivalence given in the RM means that the
 behavior of End_of_File is unspecified if the file has been positioned after
-reaching the end, or if it positioned beyond the end. Clearly, that is not
+reaching the end, or if it is positioned beyond the end. Clearly, that is not
 intended.
 
 !corrigendum A.8(01)
@@ -141,8 +143,9 @@
 @xbullet<If positioning is supported for the given external file, the function
 returns True if the current index exceeds the size of the external file;
 otherwise it returns False;>
-@xbullet<Otherwise, the function returns True if no more elements can be read from
-the given file; otherwise it returns False.>
+@xbullet<If positioning is not supported for the given external file, the
+function returns True if no more elements can be read from the given file;
+otherwise it returns False.>
 
 !ACATS test
 

Questions? Ask the ACAA Technical Agent