CVS difference for ais/ai-00178.txt

--- ais/ai-00178.txt	2003/03/04 04:56:21	1.4
+++ ais/ai-00178.txt	2003/05/24 00:51:33	1.5
@@ -1,4 +1,4 @@
-!standard 09.05.01 (18)                               03-02-20  AI95-00178/03
+!standard 09.05.01 (18)                               03-05-03  AI95-00178/04
 !class ramification 03-01-10
 !status ARG Approved 8-0-0  03-02-09
 !status work item 99-09-18
@@ -31,7 +31,7 @@
 
 3. Which subprograms are considered to "manipulate files"? Is any
 subprogram with a File_Type parameter, plus any counterpart that operates
-in the same way on a default file, considered to "manuipulate files", or is
+in the same way on a default file, considered to "manipulate files", or is
 manipulation of files restricted to subprograms that perform what A.8.2
 calls "File Management"? Indeed, are the file-management functions that
 query properties of an internal file (Mode, Name, Form, Is_Open) considered
@@ -46,12 +46,12 @@
 restrictions on the subprograms covered. Thus a broad interpretation seems
 intended.
 
-Could a more narrow interpretation been intended? It is clear that any
-subprogram that might call an operating system service to read or modify an
-external file has to be considered potentially blocking, since such a call can
-take an arbitrary amount of time to complete. This includes the file management
-operations (Create, Open, Close, etc.) as well as the operation that read or
-modify the contents of the file (Read, Write, Flush, etc.).
+Could narrower interpretation be intended? It is clear that any subprogram that
+might call an operating system service to read or modify an external file has
+to be considered potentially blocking, since such a call can take an arbitrary
+amount of time to complete. This includes the file management operations
+(Create, Open, Close, etc.) as well as the operations that read or modify the
+contents of the file (Read, Write, Flush, etc.).
 
 There are operations, like Form, Line_Length, etc., which probably don't need
 to call any system service, but can merely be implemented by retrieving