CVS difference for ais/ai-10260.txt

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

--- ais/ai-10260.txt	2005/01/07 03:07:46	1.6
+++ ais/ai-10260.txt	2005/02/08 07:12:42	1.7
@@ -1,4 +1,4 @@
-!standard  3.09  (06)                               04-12-01  AI95-00260-02/03
+!standard  3.09  (06)                               05-02-02  AI95-00260-02/04
 !standard  3.09  (07)
 !standard  3.09  (12)
 !standard  3.09  (18)
@@ -6,6 +6,7 @@
 !standard  3.09  (30)
 !standard  3.09.02 (01)
 !standard  3.09.02 (02)
+!standard  3.09.02 (22)
 !standard  3.09.03 (03)
 !standard  3.09.03 (11)
 !standard 12.06  (02)
@@ -149,14 +150,17 @@
 
 Change the first sentence of 3.9.2(1):
 
-The primitive subprograms of a tagged type are called *dispatching operations*,
-as are subprograms declared by a formal_abstract_subprogram_declaration.
+The primitive subprograms of a tagged type, and the
+subprograms declared by a formal_abstract_subprogram_declaration
+are called *dispatching operations*.
 
 Change the first sentence of 3.9.2(2):
 
 A *call on a dispatching operation* is a call whose name or prefix denotes the
 declaration of a dispatching operation.
 
+Change "primitive" to "dispatching" in 3.9.2(22).
+
 Change the first sentence of 3.9.3(3):
 
 A subprogram declared by an abstract_subprogram_declaration (see 6.1) or
@@ -166,7 +170,8 @@
 Replace the first sentence of 3.9.3(11) by:
 
 A generic actual subprogram shall not be an abstract subprogram unless the
-generic formal subprogram is a formal_abstract_subprogram_declaration.
+generic formal subprogram is declared by a
+formal_abstract_subprogram_declaration.
 
 
 Replace 12.6(2) by:
@@ -663,18 +668,18 @@
 polymorphism is achieved when a dispatching operation is called by a
 dispatching call.
 @dby
-The primitive subprograms of a tagged type are called @i<dispatching
-operations>, as are subprograms declared by a
-@fa<formal_abstract_subprogram_declaration>. A dispatching operation can be
-called using a statically determined @i<controlling> tag, in which case the
-body to be executed is determined at compile time. Alternatively, the
-controlling tag can be dynamically determined, in which case the call
-@i<dispatches> to a body that is determined at run time; such a call is termed
-a @i<dispatching call>. As explained below, the properties of the operands and
-the context of a particular call on a dispatching operation determine how the
-controlling tag is determined, and hence whether or not the call is a
-dispatching call. Run-time polymorphism is achieved when a dispatching
-operation is called by a dispatching call.
+The primitive subprograms of a tagged type, and the subprograms declared by a
+@fa<formal_abstract_subprogram_declaration>, are called @i<dispatching
+operations>. A dispatching operation can be called using a statically
+determined @i<controlling> tag, in which case the body to be executed is
+determined at compile time. Alternatively, the controlling tag can be
+dynamically determined, in which case the call @i<dispatches> to a body that is
+determined at run time; such a call is termed a @i<dispatching call>. As
+explained below, the properties of the operands and the context of a particular
+call on a dispatching operation determine how the controlling tag is
+determined, and hence whether or not the call is a dispatching call. Run-time
+polymorphism is achieved when a dispatching operation is called by a
+dispatching call.
 
 !corrigendum 3.9.2(2)
 
@@ -702,6 +707,19 @@
 If the call is to a (primitive) function with result type T, then the call has
 a @i<controlling result> -- the context of the call can control the dispatching.
 
+!corrigendum 3.9.2(2)
+
+@drepl
+@xindent<@s9<73  This subclause covers calls on primitive subprograms of
+a tagged type. Rules for tagged type membership tests are described
+in 4.5.2. Controlling tag determination for an @fa<assignment_statement>
+is described in 5.2).>>
+@dby
+@xindent<@s9<73  This subclause covers calls on dispatching subprograms of
+a tagged type. Rules for tagged type membership tests are described
+in 4.5.2. Controlling tag determination for an @fa<assignment_statement>
+is described in 5.2).>>
+
 !corrigendum 3.9.3(3)
 
 @drepl
@@ -723,7 +741,8 @@
 subprogram.
 @dby
 A generic actual subprogram shall not be an abstract subprogram unless the
-generic formal subprogram is a @fa<formal_abstract_subprogram_declaration>.
+generic formal subprogram is declared by a
+@fa<formal_abstract_subprogram_declaration>.
 The @fa<prefix> of an @fa<attribute_reference> for the Access,
 Unchecked_Access, or Address attributes shall not denote an abstract
 subprogram.

Questions? Ask the ACAA Technical Agent