CVS difference for ai05s/ai05-0245-1.txt

--- ai05s/ai05-0245-1.txt	2011/04/07 06:30:24	1.3
+++ ai05s/ai05-0245-1.txt	2011/04/08 01:09:19	1.4
@@ -1,6 +1,7 @@
-!standard 0.3(57.11/2)                             11-04-04    AI05-0245-1/03
+!standard 0.3(57.11/2)                             11-04-07    AI05-0245-1/04
 !class Amendment 11-03-10
 !status Amendment 2012 11-03-10
+!status ARG Approved  8-0-0  10-04-07
 !status work item 11-03-10
 !status received 11-03-10
 !priority Low
@@ -57,7 +58,7 @@
 parameters of all modes. In order to mitigate consequent (and indeed
 existing) problems of inadvertent order dependence, rules are introduced to
 reduce aliasing. A parameter may now be explicitly marked as aliased and
-incomplete types may be used as the type of a parameter in certain
+the type of a parameter may be incomplete in certain
 circumstances. See clauses 3.10.1, 6.1, and 6.4.1.
 
 * The use of access types is now more flexible. The rules for
@@ -130,7 +131,7 @@
 parameters of all modes. In order to mitigate consequent (and indeed
 existing) problems of inadvertent order dependence, rules are introduced to
 reduce aliasing. A parameter may now be explicitly marked as aliased and
-incomplete types may be used as parameters in certain circumstances. See
+the type of a parameter may be incomplete in certain circumstances. See
 clauses 3.10.1, 6.1, and 6.4.1.>
 
 @xbullet<The use of access types is now more flexible. The rules for
@@ -150,10 +151,10 @@
 bounded forms of the existing containers and new containers for indefinite
 objects, multiway trees, and queues. See clause A.18.>
 
-@xbullet<Finally, features are added primarily to ease the use of containers
-such as the ability to iterate over all elements in a container without
-having to encode the iteration. These can also be used for iteration over
-arrays. See clauses 4.1.5, 4.1.6, and 5.5.1.>
+@xbullet<Finally, certain features are added primarily to ease the use of
+containers such as the ability to iterate over all elements in a container
+without having to encode the iteration. These can also be used for
+iteration over arrays. See clauses 4.1.5, 4.1.6, and 5.5.1.>
 
 
 !ACATS test
@@ -581,15 +582,32 @@
 
 In the update to the RM Introduction:
 
-> * A number of changes are made to parameters. Functions may now have 
+> * A number of changes are made to parameters. Functions may now have
 > parameters of all modes. In order to mitigate consequent (and indeed
-> existing) problems of inadvertent order dependence, rules are 
-> introduced to reduce aliasing. A parameter may now be explicitly 
+> existing) problems of inadvertent order dependence, rules are
+> introduced to reduce aliasing. A parameter may now be explicitly
 > marked as aliased and incomplete types may be used as parameters in certain circumstances.
 
 I suggest changing: "incomplete types may be used as parameters"
                 to: "incomplete types may be used as parameter types"
 
 > See clauses 3.10.1, 6.1, and 6.4.1.
+
+****************************************************************
+
+From: John Barnes
+Sent: Thursday, April 7, 2011  3:52 AM
+
+OK. So I am reading these wretched AIs in order.
+
+My only comment on this one is that the sentence in bullet 4 recently revised to
+read
+
+"and  incomplete types may be used as the type of a parameter in certain
+circumstances"
+
+would be neater as
+
+"and the type of a parameter my be incomplete in certain circumstances"
 
 ****************************************************************