CVS difference for ais/ai-00118.txt

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

--- ais/ai-00118.txt	1999/10/08 23:41:05	1.5
+++ ais/ai-00118.txt	2000/04/14 01:45:07	1.6
@@ -1,4 +1,4 @@
-!standard 09.10    (06)                               99-08-31  AI95-00118/04
+!standard 09.10    (06)                               00-04-11  AI95-00118/05
 !class binding interpretation 96-04-04
 !status Corrigendum 2000 99-07-28
 !status WG9 approved 96-12-07
@@ -64,7 +64,7 @@
 The wording is written so that Ada.Task_Identificiation.Is_Terminated(<expr>)
 (where <expr> evaluates to T'Identity) works the same as T'Terminated. It would
 be very surprising if this function, defined to be the same as 'Terminated,
-had a different signalling behavior.
+had a different signaling behavior.
 Note that we do not say anything about the Callable attribute; if the
 Callable attribute becomes False, the task might still have a local
@@ -77,8 +77,9 @@
 waiting for the termination of the task;>
 @xbullet<If A1 is the termination of a task T, and A2
-is the evaluation of the expression T'Terminated or a call to
-Ada.Task_Identification.Is_Terminated where the parameter identifies T;>
+is either the evaluation of the expression T'Terminated or a call to
+Ada.Task_Identification.Is_Terminated with an actual parameter that identifies
+T (see C.7.1);>
 !ACATS test
@@ -142,7 +143,7 @@
 I agree with your analysis and I also agree that it would be *nice* if
-termination would be folded in the signalling concept. But:
+termination would be folded in the signaling concept. But:
 > Clearly, one would like this idiom to work as "expected" and shared
 > variables, whose changed values are cached by the implementation of local

Questions? Ask the ACAA Technical Agent