CVS difference for ais/ai-00256.txt

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

--- ais/ai-00256.txt	2003/03/04 04:56:22	1.9
+++ ais/ai-00256.txt	2003/05/24 00:51:36	1.10
@@ -1,4 +1,4 @@
-!standard 13.11.01 (01)                                03-02-20  AI95-00256/07
+!standard 13.11.01 (01)                                03-05-02  AI95-00256/08
 !standard  A.12.01 (30)
 !standard  G.02.02 (03)
 !standard  7.06.01 (16)
@@ -19,10 +19,8 @@
 
 !summary
 
-(Note: This AI contains various wording changes that ought to be made to the
-standard for which there is expected to be no opposition to the change. The
-intent is that this AI will only be processed when a Corrigendum or Amendment
-is about to be issued.)
+(Note: This AI contains various wording changes that for which it was expected
+that there would be no opposition to the change.)
 
 1) The value of the Max_Size_In_Storage_Elements attribute is the maximum value
 that could be requested by the implementation.
@@ -64,7 +62,7 @@
 (or write) if the file supports positioning? (At the current index.)
 
 Nowhere in A.12.1 is this specified. Defect Report 8652/0055 says that the
-intent is that stream files with positioning act like Dirct_IO files. Is
+intent is that stream files with positioning act like Direct_IO files. Is
 it OK for an implementation to ignore the current index of a stream file? (No.)
 
 3)
@@ -86,9 +84,9 @@
 (Yes.)
 
 6)
-AI-00180 says that "mentioned" is used "informally" in 10.2(9); it it not
+AI-00180 says that "mentioned" is used "informally" in 10.2(9); it is not
 intended to mean the technical term "mentioned". Should this be reworded to
-avoid the use of the technical term. (Yes.)
+avoid the use of the technical term? (Yes.)
 
 7)
 AI-00212 changes 10.1.5(9). However, AI-00069 depended on 10.1.5(9) in order to
@@ -110,11 +108,11 @@
 1)
 The intent of the Max_Size_In_Storage_Elements attribute is that it supplies an
 upper bound on the memory that will be requested from Allocate. Certainly,
-there was no intent that the value returned depend on the execution of the
+there was no intent that the value returned depends on the execution of the
 program. Thus, we adjust the wording to say clearly what was meant.
 
 2)
-Defect Report 8652/0055 make it clear that the model of stream files with
+Defect Report 8652/0055 makes it clear that the model of stream files with
 positioning is to be the same as Direct_IO files. Unfortunately, the wording
 with that Defect Report failed to say where Read and Write without an index
 parameter read or write. Compare A.12.1(30) to A.8.5(3) to see the missing text.
@@ -127,7 +125,7 @@
 4)
 Defect Report 8652/0024 clearly differentiates between "assignment statements"
 and "initialization by assignment". It never discusses anything that isn't
-one or the other; the authors appearently thought that there were no other
+one or the other; the authors apparently thought that there were no other
 possibilities. All of the other cases of assignment operations are very
 similar to "initialization", and thus should be treated the same way; this
 was the expectation of the authors of the previous report.
@@ -174,8 +172,8 @@
 are performed, and then Program_Error is raised.>
 @dby
 @xbullet<For an Adjust invoked as part of assignment operations other than those
-invoked as part of an assignment statment, other adjustments due to be performed
-might or might not be performed, and then Program_Error is raised.
+invoked as part of an assignment statement, other adjustments due to be
+performed might or might not be performed, and then Program_Error is raised.
 During its propagation, finalization might or might not be applied to objects
 whose Adjust failed. For an Adjust invoked as part of an assignment statement,
 any other adjustments due to be performed are performed, and then Program_Error

Questions? Ask the ACAA Technical Agent