CVS difference for ais/ai-00206.txt

Differences between 1.3 and version 1.4
Log of other versions for file ais/ai-00206.txt

--- ais/ai-00206.txt	1999/02/28 01:43:02	1.3
+++ ais/ai-00206.txt	1999/06/22 01:44:37	1.4
@@ -1,5 +1,6 @@
-!standard C.7.1    (10)                               98-09-29  AI95-00206/00
+!standard C.7.1    (10)                               99-06-12  AI95-00206/01
 !class ramification 98-09-29
+!status WG9 approved 99-06-12
 !status ARG Approved (7-0-0)  98-10-08
 !status work item 98-09-29
 !status received 98-09-29
@@ -7,21 +8,21 @@
 !difficulty Easy
 !subject Ada.Task_Identification.Is_Callable for the environment task
 
-!summary 98-09-29
+!summary
 
 Ada.Task_Identification.Is_Callable called with a Task_Id value designating
 the environment task returns True while the main subprogram is executing and
 False once the main subprogram has returned and the environment task starts
 waiting for library-level tasks to terminate.
 
-!question 98-09-29
+!question
 
-What is the behavior of Ada.Task_Identification.Is_Callable for the 
+What is the behavior of Ada.Task_Identification.Is_Callable for the
 environment task? In particular, does it change in value from True to False
 when the main subprogram exits and starts waiting for library-level tasks
 to terminate? (Yes)
 
-!response 98-09-29
+!response
 
 The note C.7.1(21) says that Ada.Task_Identification.Current_Task can return a
 Task_Id value designating the environment task. The definition of Is_Callable
@@ -44,7 +45,7 @@
 reusable package containing a library task. At least one commercial Ada
 library uses this technique.
 
-!appendix 98-09-29
+!appendix
 
 !topic Is_Callable and the environment task.
 !reference RM95-C.7.1(10);6.0
@@ -82,25 +83,25 @@
 best minds in Ada seem to think otherwise; therefore I'm submitting the question
 to the ARG.
 
-The value of Is_Callable would be useful to determine whether the main 
-subprogram has completed. A package with embedded tasks could use this 
-information to determine when to terminate, without requiring any 
-cooperation from the main program.  This is of benefit to "canned" 
-packages, which ought to be designed to work even in the face of common 
-user errors. For instance, needing a "Shutdown" routine makes a package 
-more fragile, because it is easy for the user of the package to forget to 
-call the routine (or an exception propagates past the call, causing it not 
+The value of Is_Callable would be useful to determine whether the main
+subprogram has completed. A package with embedded tasks could use this
+information to determine when to terminate, without requiring any
+cooperation from the main program.  This is of benefit to "canned"
+packages, which ought to be designed to work even in the face of common
+user errors. For instance, needing a "Shutdown" routine makes a package
+more fragile, because it is easy for the user of the package to forget to
+call the routine (or an exception propagates past the call, causing it not
 to be called).
 
-If a "canned" package includes a task, it is important that the task be 
-able to terminate itself appropriately. Unfortunately, finalization cannot 
-be used for this purpose, since library-level tasks must terminate before 
-any library-level objects are finalized. Therefore, another technique must 
-be used. If the task cannot sit on a terminate alternative (perhaps because 
-it must poll a resource), a function which returns the status of the 
+If a "canned" package includes a task, it is important that the task be
+able to terminate itself appropriately. Unfortunately, finalization cannot
+be used for this purpose, since library-level tasks must terminate before
+any library-level objects are finalized. Therefore, another technique must
+be used. If the task cannot sit on a terminate alternative (perhaps because
+it must poll a resource), a function which returns the status of the
 environment task is another solution - and Ada 95 already has the function.
 
-This problem has arisen in Claw in the task which handles Window messages, 
+This problem has arisen in Claw in the task which handles Window messages,
 it is not academic.
 
 
@@ -119,9 +120,9 @@
 <<reference as: 1998-15877.a Tucker Taft 1998-8-8>>
 !discussion
 
-> What is the behavior of Ada.Task_Identification.Is_Callable for the 
+> What is the behavior of Ada.Task_Identification.Is_Callable for the
 > environment task?
-> In particular, does it change in value from True to False when the main 
+> In particular, does it change in value from True to False when the main
 > subprogram
 > exits and starts waiting for library-level tasks to terminate?
 
@@ -131,11 +132,11 @@
 to imply that it should go from true to false upon return from
 the main subprogram.
 
-> ... If the task cannot sit on a terminate alternative (perhaps because 
-> it must poll a resource), a function which returns the status of the 
+> ... If the task cannot sit on a terminate alternative (perhaps because
+> it must poll a resource), a function which returns the status of the
 > environment task is another solution - and Ada 95 already has the function.
-> 
-> This problem has arisen in Claw in the task which handles Window messages, 
+>
+> This problem has arisen in Claw in the task which handles Window messages,
 > it is not academic.
 
 This shows that making Is_Callable work "right" for the environment
@@ -173,7 +174,7 @@
 I believe the ARM intentionally leaves this unspecified.
 
 ...
-| The value of Is_Callable would be useful to determine whether the main 
+| The value of Is_Callable would be useful to determine whether the main
 | subprogram has completed.
 
 I can see that it would be useful.
@@ -234,7 +235,7 @@
 !from Ted Baker 1998-8-12
 <<reference as: 1998-15882.a Ted Baker  1998-8-12>>
 !discussion
-| 
+|
 | >| What is the behavior of Ada.Task_Identification.Is_Callable for
 | >| the environment task?  In particular, does it change in value from
 | >| True to False when the main subprogram exits and starts waiting

Questions? Ask the ACAA Technical Agent