From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e2e6547249e6f9d1 X-Google-Attributes: gid103376,public From: ncohen@watson.ibm.com (Norman H. Cohen) Subject: Re: How to wait for task completion Date: 1996/09/17 Message-ID: <51mhns$jif@watnews1.watson.ibm.com>#1/1 X-Deja-AN: 181150566 distribution: world references: <01bba2e8$c45aad90$35208b82@wd> <01bba3f7$ee398fe0$10208b82@wd> organization: IBM T.J. Watson Research Center reply-to: ncohen@watson.ibm.com newsgroups: comp.lang.ada Date: 1996-09-17T00:00:00+00:00 List-Id: In article , Samuel Tardieu writes: |> >>>>> "wiljan" == wiljan writes: |> ... |> wiljan> In my case I want |> wiljan> to clean up the task object itself by using |> wiljan> ada.unchecked_deallocation. |> |> So you should have a look at the generic package Ada.Task_Attributes: |> it lets you attach special attributes onto task running on your |> system. If you attach an attribute of a controlled type to your task, |> then it will be destroyed (this the Finalization procedure called) |> whenever the task is completed. Indeed, RM95-C.7.2(17) guarantees this. However, unlike Ada 83, Ada 95 does not guarantee that unchecked deallocation will reclaim the storage for a task object (or for a composite object with a subcomponent that is a task object), even if the task has terminated when the deallocation procedure is called! See the last sentence of RM95-13.11.2(9). I hope none of the implementors has read this sentence. :-) -- Norman H. Cohen ncohen@watson.ibm.com