CVS difference for ais/ai-00085.txt

Differences between 1.7 and version 1.8
Log of other versions for file ais/ai-00085.txt

--- ais/ai-00085.txt	2002/03/13 00:48:25	1.7
+++ ais/ai-00085.txt	2002/05/25 03:42:17	1.8
@@ -1,14 +1,16 @@
-!standard A.8.2    (16)                               02-02-25  AI95-00085/07
+!standard A.8.2    (16)                               02-05-09  AI95-00085/08
+!standard A.12.1(28.1)
 !standard A.12.1(33)
 !class confirmation 95-08-19
+!status Amendment 200Y 02-05-09
 !status ARG Approved 6-0-1  02-02-12
 !status work item 98-10-09
-!status ARG approved (subject to editorial review) 12-0-0  98-04-03
+!status ARG Approved (subject to editorial review) 12-0-0  98-04-03
 !status work item 95-11-01
 !status received 95-08-19
 !priority High
 !difficulty Hard
-!subject Append_File, Reset and positioning for Stream_IO
+!subject Append_File, Reset, and positioning for Stream_IO
 
 !summary
 
@@ -20,8 +22,8 @@
 file.
 
 It is legitimate for an implementation to raise Use_Error on the
-positioning operations of Stream_IO in the circumstances where the
-underlying operating system does not support positioning.
+positioning operations of Stream_IO if the underlying operating system
+does not support positioning.
 
 The procedure Stream_IO.Set_Mode sets the mode of the file, it doesn't
 necessarily change it.
@@ -44,7 +46,7 @@
    files opened in Append_File mode, what are the possible effects of
    Set_Index? (Do the right thing or raise Use_Error.)
 
-4. A.12.1(35) says that "the Set_Mode procedure changes the mode of
+4. A.12.1(28.1/1) says that "the Set_Mode procedure changes the mode of
    file."  Does that mean that Set_Mode can only be used to "change" the
    mode of the file? (No.)
 
@@ -83,11 +85,11 @@
 to In_File or Out_File must be implemented by closing and reopening.
 
 3. It is the intent that a Unix implementation can use the Unix append
-mode to implement files opended in Append_File mode. For a stream
+mode to implement files opened in Append_File mode. For a stream
 designating such a file, positioning is effectively impossible because,
 if the O_APPEND bit was set at open time, "the file pointer is set to the
 end of the file prior to each write" (excerpt from the Unix man page
-for open). A.12.1(32) makes it clear that such an implementation
+for open). A.12.1(33) makes it clear that such an implementation
 is legitimate, provided that it raises Use_Error on the positioning
 operations: "if positioning is not supported for the given file, then a
 call to Index or Set_Index propagates Use_Error."
@@ -105,14 +107,25 @@
 is that the file and stream operations should be implemented as a thin
 layer on top of the OS calls, and should not have to simulate services
 that are not provided by the underlying OS. Moreover, since there is no
-requirement to support positioning on any stream files, a truly portable
-program would have to avoid positioning of stream files in any mode. Thus,
+requirement to support positioning for any stream files, a truly portable
+program would have to avoid positioning a stream file in any mode. Thus,
 allowing implementations to use O_APPEND does not impose any further
 portability penalty.
 
-4. A.12.1(35) should say that "the procedure Set Mode sets the mode
+4. A.12.1(28.1/1) should say that "the procedure Set_Mode sets the mode
 of the file."  If the Mode parameter is the current mode of the file,
 then surely the mode of the file is not changed.
+
+!corrigendum A.12.1(28.1/1)
+
+@drepl
+The Set_Mode procedure changes the mode of the file. If the new mode is
+Append_File, the file is positioned to its end; otherwise, the position in
+the file is unchanged.
+@dby
+The Set_Mode procedure sets the mode of the file. If the new mode is
+Append_File, the file is positioned to its end; otherwise, the position in
+the file is unchanged.
 
 !appendix
 

Questions? Ask the ACAA Technical Agent