CVS difference for ai12s/ai12-0445-1.txt

Differences between 1.2 and version 1.3
Log of other versions for file ai12s/ai12-0445-1.txt

--- ai12s/ai12-0445-1.txt	2022/05/04 00:03:04	1.2
+++ ai12s/ai12-0445-1.txt	2022/05/07 06:14:18	1.3
@@ -1,5 +1,7 @@
-!standard 3.2(8)                                       22-05-02  AI12-0445-1/02
+!standard 3.2(8)                                       22-05-05  AI12-0445-1/03
 !standard 3.10.2(20)
+!standard 5.5.3(21/5)
+!standard 5.5.3(27/5)
 !standard 5.5.3(28/5)
 !standard 5.5.3(29/5)
 !standard 7.6.1(16/2)
@@ -42,6 +44,8 @@
 !standard D.15(1/3)
 !standard G(4)
 !class presentation 22-04-28
+!status Amendment 1-2012 22-05-05
+!status ARG Approved 14-0-0  22-05-05
 !status work item 22-04-28
 !status received 22-02-18
 !priority Critical
@@ -97,6 +101,32 @@
 
 [Replace "needed" - Editor.]
 
+Modify 5.5.3(21/5):
+
+     Specifying the Parallel_Iterator aspect to be True for a
+     callable entity indicates that the entity {is allowed to}[might] invoke
+     the loop body procedure from multiple distinct logical threads of
+     control. The Parallel_Iterator aspect for a subprogram shall
+     be statically False if the subprogram allows exit.
+
+["Might" is clearly better that "can" here, so we need a more substantial 
+rewording. - Editor.]
+
+Modify 5.5.3(27/5):
+
+    For the execution of a loop_statement with an iteration_scheme that has a
+    procedural_iterator, the procedure denoted by the name or prefix of the
+    iterator_procedure_call (the iterating procedure) is invoked, passing an
+    access value designating the loop body procedure as a parameter. The iterating
+    procedure then calls the loop body procedure zero or more times and returns,
+    whereupon the loop_statement is complete. If the parallel reserved word is
+    present, the iterating procedure {is allowed to}[might] invoke the loop body
+    procedure from multiple distinct logical threads of control. The
+    aspect_specification, if any, is elaborated prior to the invocation of
+    the iterating procedure.
+
+[See previous item. - Editor.]
+
 Modify 5.5.3(28/5):
 
     If the callable entity identified in the iterator_procedure_call allows
@@ -629,7 +659,7 @@
 as all of the related paragraphs use both "need not" and "could cause".]
 
 Note that while some phrases are given meanings, other uses of the words seem
-be to be allowed by the Directives. For instance, "necessary" is used in many
+to be allowed by the Directives. For instance, "necessary" is used in many
 contexts in the Directives that are not requirements.
 
 We handle occurrences of "must" in AI12-0438-1, and simple changes where some
@@ -659,7 +689,7 @@
 We might be able to argue that "need" is not mentioned in the drafting
 document, but even so we ought to get rid of as many of those as possible.
 
-There is nearly 200 paragraphs here that probably need fixing, and there is
+There are nearly 200 paragraphs here that probably need fixing, and there is
 not a one-size-fits all solution. Many of the occurrences of "could" and
 "might" could be replaced by "can", but certainly not all.
 

Questions? Ask the ACAA Technical Agent