CVS difference for ais/ai-00416.txt
--- ais/ai-00416.txt 2005/04/13 05:37:23 1.5
+++ ais/ai-00416.txt 2005/04/14 22:16:12 1.6
@@ -1,4 +1,4 @@
-!standard 3.2.3(01) 05-03-10 AI95-00416/04
+!standard 3.2.3(01) 05-04-13 AI95-00416/05
!standard 3.7(27)
!standard 3.9.2(02)
!standard 3.9.2(04)
@@ -136,8 +136,8 @@
Change 3.7(27) to:
- For an access discriminant, an access_definition is elaborated when
- the value of the corresponding access discriminant is defined: by
+ For an access discriminant, its access_definition is elaborated when
+ the value of the access discriminant is defined: by
evaluation of its default_expression, by elaboration of a
discriminant_constraint, or by an assignment that initializes the
enclosing object.
@@ -174,7 +174,7 @@
Change 3.9.2(18):
* If the call has a controlling result {or controlling access result} and
- is itself{, or designates,} a [(possibly parenthesized or qualified)]
+ is itself{, or designates,} a (possibly parenthesized or qualified)
controlling operand of an enclosing call on a dispatching operation of a
descendant of type T, then its controlling tag value is determined
by the controlling tag value of this enclosing call;
@@ -195,7 +195,8 @@
there is no Ada95 compatibility issue, and there is no automatic
null check inherent in the use of a controlling access result. If a
null check is necessary, it is because there is a dereference of the
- result. If there is no dereference of the result, a null return
+ result, or because the value is passed to a null-excluding parameter.
+ If there is no dereference of the result, a null return
value is perfectly acceptable, and can be a useful indication of a
particular status of the call.
@@ -443,7 +444,7 @@
Change 9.2(4):
- {For tasks that are part a single object that is not a stand-alone
+ {For tasks that are part of a single object that is not a stand-alone
object, activations are initiated after completing any
initialization of the outermost object enclosing these tasks, prior
to performing any other operation on the outermost object. In
@@ -570,8 +571,8 @@
type. When the expression defining the access discriminant is evaluated, it is
converted to this anonymous access type (see 4.6).
@dby
-For an access discriminant, an @fa<access_definition> is elaborated when
-the value of the corresponding access discriminant is defined: by
+For an access discriminant, its @fa<access_definition> is elaborated when
+the value of the access discriminant is defined: by
evaluation of its @fa<default_expression>, by elaboration of a
@fa<discriminant_constraint>, or by an assignment that initializes the
enclosing object.
@@ -671,9 +672,10 @@
determined by the controlling tag value of this enclosing call;>
@dby
@xbullet<If the call has a controlling result or controlling access result and
-is itself, or designates, a controlling operand of an enclosing call on a
-dispatching operation of a descendant of type @i<T>, then its controlling tag
-value is determined by the controlling tag value of this enclosing call;>
+is itself, or designates, a (possibly parenthesized or qualified) controlling
+operand of an enclosing call on a dispatching operation of a descendant of type
+@i<T>, then its controlling tag value is determined by the controlling tag
+value of this enclosing call;>
@xbullet<If the call has a controlling result or controlling access result and
(possibly parenthesized, qualified, or dereferenced) is the expression of an
@@ -958,12 +960,13 @@
responsible for its creation.
@dby
A task object (which represents one task) can be a part of a
-stand-alone object, of an object created by an allocator, or of an
+stand-alone object, of an object created by an @fa<allocator>, or of an
anonymous object of a limited type. All tasks that are part of any
-of the stand-alone objects created by the elaboration of @fa<object_declaration>s (or
-@fa<generic_association>s of formal objects of mode @b<in>) of a single declarative region are activated together. All
-tasks that are part of a single object that is not a stand-alone
-object are activated together.
+of the stand-alone objects created by the elaboration of
+@fa<object_declaration>s (or @fa<generic_association>s of formal objects of
+mode @b<in>) of a single declarative region are activated together. All tasks
+that are part of a single object that is not a stand-alone object are activated
+together.
!corrigendum 9.2(03)
@@ -993,7 +996,7 @@
any initialization for the object created by the @fa<allocator>, and prior to
returning the new access value.
@dby
-For tasks that are part a single object that is not a stand-alone
+For tasks that are part of a single object that is not a stand-alone
object, activations are initiated after completing any
initialization of the outermost object enclosing these tasks, prior
to performing any other operation on the outermost object. In
Questions? Ask the ACAA Technical Agent