CVS difference for ais/ai-00162.txt

Differences between 1.10 and version 1.11
Log of other versions for file ais/ai-00162.txt

--- ais/ai-00162.txt	2005/05/15 23:39:37	1.10
+++ ais/ai-00162.txt	2005/06/16 23:47:09	1.11
@@ -1,4 +1,4 @@
-!standard 03.10.02 (3)                               05-03-24  AI95-00162/07
+!standard 03.10.02 (3)                               05-06-15  AI95-00162/08
 !standard 03.10.02 (7)
 !standard 03.10.02 (13)
 !standard 06.05 (18)
@@ -120,11 +120,11 @@
   The master of an object is the master enclosing its creation whose
   accessibility level (see 3.10.2) is equal to that of the object.
 
-  In the case of a potentially blocking operation which is a master,
-  finalization of an (anonymous) object occurs before blocking if the last use of
-  the object occurs before blocking. In particular, for a delay_statement, any
-  finalization occurs before delaying the task.
-  In the case of an expression which is a master,
+  In the case of a potentially blocking operation that is a master,
+  finalization of an (anonymous) object occurs before blocking if the last use
+  of the object occurs before blocking. In particular, for a delay_statement,
+  any finalization occurs before delaying the task.
+  In the case of an expression that is a master,
   finalization of any (anonymous) objects occurs as the final part of
   evaluation of the expression.
 
@@ -350,7 +350,7 @@
 @drepl
 The accessibility rules, which prevent dangling references, are written in
 terms of @i<accessibility levels>, which reflect the run-time nesting of
-masters. As explained in 7.6.1, a master is the execution of a @fa<task_body>,
+@i<masters>. As explained in 7.6.1, a master is the execution of a @fa<task_body>,
 a @fa<block_statement>, a @fa<subprogram_body>, an @fa<entry_body>, or an
 @fa<accept_statement>. An accessibility level is @i<deeper than> another if it
 is more deeply nested at run time. For example, an object declared local to a
@@ -364,7 +364,7 @@
 @dby
 The accessibility rules, which prevent dangling references, are written in
 terms of @i<accessibility levels>, which reflect the run-time nesting of
-masters (see 7.6.1). An accessibility level is @i<deeper than> another if it
+@i<masters> (see 7.6.1). An accessibility level is @i<deeper than> another if it
 is more deeply nested at run time. For example, an object declared local to a
 called subprogram has a deeper accessibility level than an object declared
 local to the calling subprogram. The accessibility rules for access types
@@ -415,15 +415,15 @@
 After execution of a construct or entity is complete, it is @i<left>, meaning
 that execution continues with the next action, as defined for the execution
 that is taking place. Leaving an execution happens immediately after its
-completion, except in the case of a master: the execution of a @fa<task_body>, a
-@fa<block_statement>, a @fa<subprogram_body>, an @fa<entry_body>, or an
-@fa<accept_statement>. A master is finalized after it is complete, and before
-it is left.
+completion, except in the case of a @i<master>: the execution of a
+@fa<task_body>, a @fa<block_statement>, a @fa<subprogram_body>, an
+@fa<entry_body>, or an @fa<accept_statement>. A master is finalized after it is
+complete, and before it is left.
 @dby
 After execution of a construct or entity is complete, it is @i<left>, meaning
 that execution continues with the next action, as defined for the execution
 that is taking place. Leaving an execution happens immediately after its
-completion, except in the case of a master: the execution of a body other
+completion, except in the case of a @i<master>: the execution of a body other
 than a @fa<package_body>; the elaboration of a declaration other than the
 declaration of a package; the execution of an @fa<accept_statement>, a
 @fa<block_statement>, or a @fa<simple_statement>; or the evaluation of an
@@ -456,11 +456,11 @@
 part of the finalizations due to be performed for the object's innermost
 enclosing master.
 @dby
-In the case of a potentially blocking operation which is a master,
+In the case of a potentially blocking operation that is a master,
 finalization of an (anonymous) object occurs before blocking if the last use of
 the object occurs before blocking. In particular, for a @fa<delay_statement>,
 any finalization occurs before delaying the task.
-In the case of an @fa<expression> which is a master,
+In the case of an @fa<expression> that is a master,
 finalization of any (anonymous) objects occurs as the final part of
 evaluation of the @fa<expression>.
 

Questions? Ask the ACAA Technical Agent