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

Differences between 1.5 and version 1.6
Log of other versions for file ai12s/ai12-0220-1.txt

--- ai12s/ai12-0220-1.txt	2018/04/06 04:52:02	1.5
+++ ai12s/ai12-0220-1.txt	2018/04/07 06:19:15	1.6
@@ -232,15 +232,14 @@
 !corrigendum 6.1.1(2/3)
 
 @drepl
-@xhang<@xterm<Pre>
-  This aspect defines a specific precondition for a callable entity; it
+@xhang<@xterm<Pre>This aspect specifies a specific precondition for a
+  callable entity; it
   shall be specified by an @fa<expression>, called a @i<specific precondition
   expression>. If not specified for an entity, the specific precondition
   expression for the entity is the enumeration literal True.>
 @dby
-@xhang<@xterm<Pre>
-  This aspect defines a specific precondition for a callable entity or an
-  access-to-subprogram type; it shall
+@xhang<@xterm<Pre>This aspect specifies a specific precondition for a
+  callable entity or an access-to-subprogram type; it shall
   be specified by an @fa<expression>, called a @i<specific precondition
   expression>. If not specified for an entity, the specific precondition
   expression for the entity is the enumeration literal True.>
@@ -248,15 +247,14 @@
 !corrigendum 6.1.1(4/3)
 
 @drepl
-@xhang<@xterm<Post>
-  This aspect specifies a specific postcondition for a callable entity; it
+@xhang<@xterm<Post>This aspect specifies a specific postcondition for a
+  callable entity; it
   shall be specified by an @fa<expression>, called a @i<specific postcondition
   expression>. If not specified for an entity, the specific postcondition
   expression for the entity is the enumeration literal True.>
 @dby
-@xhang<@xterm<Post>
-  This aspect specifies a specific postcondition for a callable entity or an
-  access-to-subprogram type; it shall
+@xhang<@xterm<Post>This aspect specifies a specific postcondition for a
+  callable entity or an access-to-subprogram type; it shall
   be specified by an @fa<expression>, called a @i<specific postcondition
   expression>. If not specified for an entity, the specific postcondition
   expression for the entity is the enumeration literal True.>
@@ -299,7 +297,7 @@
    a postcondition expression for F, denotes the return object of the
    function call for which the postcondition expression is evaluated.
    The type of this attribute is that of the result subtype of the
-   of the function or access-to-function type except within a Post'Class
+   function or access-to-function type except within a Post'Class
    postcondition expression for a function with a controlling result or with a
    controlling access result; in those cases the type of the attribute was
    described previously.>
@@ -1529,5 +1527,38 @@
 
 P.P.P.S. You can look at these changes when you do your own editorial review.
 The above is mine. :-)
+
+****************************************************************
+
+From: Tucker Taft
+Sent: Friday, April 6, 2018  7:53 AM
+
+> ...
+> So the best I can do using actually defined terms would be (I'm not 
+> showing the changes in order to keep some readability):
+> 
+> Within a postcondition expression for F, denotes the return object of 
+> the function call for which the postcondition expression is evaluated.
+> The type of this attribute is that of the result subtype of the 
+> function or access-to-function type except within a Post'Class 
+> postcondition
+> 
+> expression for a function with a controlling result or with a 
+> controlling access result; in those cases the type of the attribute 
+> was described previously.
+> 
+> 
+> Improvements? Brickbats??
+
+Your rewording looks good to me.
+
+
+> P.S. I'm not so silly to try to change all of the other uses of these 
+> terms; I'd probably try to define the terms somewhere. But since that 
+> wouldn't fix the problem at hand anyway, I'm not bothering for now and 
+> am just changing this text to use actually defined terms.
+
+Yes, we should probably eventually replace "result object" with "return object"
+and "return subtype" with "result subtype" to be consistent.
 
 ****************************************************************

Questions? Ask the ACAA Technical Agent