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

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

--- ai12s/ai12-0233-1.txt	2017/10/12 04:36:53	1.6
+++ ai12s/ai12-0233-1.txt	2017/11/30 04:18:02	1.7
@@ -1,5 +1,6 @@
-!standard 6.1.1(38/4)                                  17-10-12  AI12-0233-1/03
+!standard 6.1.1(38/4)                                  17-11-17  AI12-0233-1/04
 !class ramification 17-10-12
+!status ARG Approved 6-0-2  17-10-13
 !status work item 17-06-09
 !status received 17-04-13
 !priority Low
@@ -56,7 +57,7 @@
 
 Unlike the Pre aspect, the applicable Pre'Class aspect at the point of
 call is determined by the *entity* denoted by the name used in the call,
-as apposed to the body invoked.  What this means is that upon entry to
+as opposed to the body invoked.  What this means is that upon entry to
 the invoked body, the body may presume only the weakest Pre'Class
 condition that a caller might have checked.
 
@@ -109,24 +110,9 @@
 the subprogram declaration illegal (since the declaration is implicit, so
 such a rule really affects the type declaration). That would be incompatible,
 but only at the margins (only for routines with non-trivial preconditions
-that are overriding). We have chosen the compatible approach for now,
-the a compiler or other tool could certainly enforce a restriction against
-this sort of overriding.
-
-Note that there is a separate issue, probably deserving its own AI,
-having to do with renaming-as-body.  Because a renaming-as-body is a
-distinct entity from the renamed subprogram, a renaming-as-body should
-probably be illegal unless Pre'Class of True applies to the renamed
-subprogram, or any Pre'Class aspect that applies to the renamed
-subprogram also applies to the renaming.  This is a modest
-generalization of the rule in 6.1.1(17/3):
-
-  If a renaming of a subprogram or entry S1 overrides an inherited
-  subprogram S2, then the overriding is illegal unless each class-wide
-  precondition expression that applies to S1 fully conforms to some
-  class-wide precondition expression that applies to S2 and each
-  class-wide precondition expression that applies to S2 fully conforms
-  to some class-wide precondition expression that applies to S1.
+that are overriding). We have chosen the compatible approach for now; a
+compiler or other tool could certainly enforce a restriction against this sort
+of overriding.
 
 !ASIS
 

Questions? Ask the ACAA Technical Agent