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

Differences between 1.24 and version 1.25
Log of other versions for file ai12s/ai12-0079-1.txt

--- ai12s/ai12-0079-1.txt	2018/12/14 08:31:29	1.24
+++ ai12s/ai12-0079-1.txt	2019/01/04 23:34:40	1.25
@@ -1,4 +1,7 @@
-!standard 6.1.2(0)                                  18-12-10    AI12-0079-1/10
+!standard 6.1.2(0)                                  19-01-04    AI12-0079-1/11
+!standard 13.1.1(4/3)
+!standard 13.1.1(11/3)
+!standard 13.14(3/5)
 !class Amendment 13-06-28
 !status Amendment 1-2012 18-12-10
 !status ARG Approved 11-0-1  18-12-10
@@ -31,7 +34,7 @@
 of any user-defined functions used in the aspects are available. This is
 bad, as it prevents analysis of programs as they are constructed. If the body is
 not available, no analysis is possible. Moreover, analysis depending on a body
-require creating pseudo body dependencies (if the body is changed, any analysis
+requires creating pseudo body dependencies (if the body is changed, any analysis
 depending on the properties of that body would have to be performed again); but
 the language does not allow these to be "real" body dependencies (any
 recompilation needed has to occur automatically).
@@ -172,7 +175,7 @@
       | ACCESS subtype_mark
 
    A /global_/attribute_reference is an attribute_reference with attribute
-   designator "Global."
+   designator "Global".
 
    The Global aspect identifies the set of variables (which, for the purposes
    of this clause includes all task objects) global to a callable
@@ -249,7 +252,7 @@
 An implementation-defined global_mode_qualifier may be specified, which
 reduces the set according to an implementation-defined rule.
 
-The overall set of objects associated with each global_mode include all
+The overall set of objects associated with each global_mode includes all
 objects identified for the mode in the
 primitive_global_aspect_definition (subject to the
 global_mode_qualifier), if any, plus all objects associated with the
@@ -322,7 +325,7 @@
 
 Implementation Permissions
 
-For a call on an subprogram that has a Global aspect that indicates 
+For a call on a subprogram that has a Global aspect that indicates 
 that there are no references to global variables, the implementation 
 may omit the call:
  * if the results are not needed after the call; or
@@ -358,7 +361,7 @@
 parameters on a subprogram whose Global aspect only indicates reading 
 of a global object G, then the second call be omitted and reuse the 
 result of the first call if the compiler can prove (with the help of 
-the Global aspect of any subprograms called) that G is not written 
+the Global aspect of any subprograms called) that G is not written to
 between the calls.
 End AARM Discussion.
  

Questions? Ask the ACAA Technical Agent