CVS difference for ais/ai-00397.txt

Differences between 1.7 and version 1.8
Log of other versions for file ais/ai-00397.txt

--- ais/ai-00397.txt	2005/08/05 04:37:13	1.7
+++ ais/ai-00397.txt	2005/08/21 06:00:39	1.8
@@ -1,5 +1,4 @@
-!standard 6.3.1(24)                                    05-07-11  AI95-00397/06
-!standard 6.4(10)
+!standard 6.3.1(24)                                    05-08-07  AI95-00397/07
 !standard 8.3.1(1)
 !standard 9.1(9.1)
 !standard 9.4(11)
@@ -44,9 +43,6 @@
 Also, fix the "implemented by" rules to be rechecked in the private part of
 generic instances (certainly, we want these rules to be enforced everywhere).
 
-Also, add a description of the dynamic semantics of calls to "implemented by"
-subprograms.
-
 Finally, add legality rules to prohibit primitive operations with matching
 prefixed view profiles.
 
@@ -66,16 +62,6 @@
 convention as protected operations.
 
 
-Add after 6.4(10):
-
-If the name or prefix of a subprogram call denotes an inherited
-subprogram implemented by an entry or protected subprogram (see 9.1 and
-9.4), the subprogram call is equivalent to a call on the underlying entry
-or protected subprogram, with the target object being given by the first
-actual parameter of the call, and the actual parameters of the entry or
-protected subprogram being given by the remaining actual parameters of the
-call, if any.
-
 Modify the first legality paragraph in the 8.3.1 clause added by AI-218-3 as
 follows:
 
@@ -246,25 +232,6 @@
 profile for a parameterless subprogram. For the purposes of defining subtype
 and mode conformance, the convention of a prefixed view profile is considered
 to match that of either an entry or a protected operation.
-
-!corrigendum 6.4(10)
-
-@dinsa
-For the execution of a subprogram call, the @fa<name> or @fa<prefix> of the
-call is evaluated, and each @fa<parameter_association> is evaluated (see
-6.4.1). If a @fa<default_expression> is used, an implicit
-@fa<parameter_association> is assumed for this rule. These evaluations are done
-in an arbitrary order. The @fa<subprogram_body> is then executed. Finally, if
-the subprogram completes normally, then after it is left, any necessary
-assigning back of formal to actual parameters occurs (see 6.4.1).
-@dinst
-If the @fa<name> or @fa<prefix> of a subprogram call denotes an inherited
-subprogram implemented by an entry or protected subprogram (see 9.1 and
-9.4), the subprogram call is equivalent to a call on the underlying entry
-or protected subprogram, with the target object being given by the first
-actual parameter of the call, and the actual parameters of the entry or
-protected subprogram being given by the remaining actual parameters of the
-call, if any.
 
 !corrigendum 8.3.1(1)
 !comment This is a dummy just to cause a conflict.

Questions? Ask the ACAA Technical Agent