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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c24a60e907705f00 X-Google-Attributes: gid103376,public From: stt@houdini.camb.inmet.com (Tucker Taft) Subject: Re: is_callable(environment)? Date: 1998/07/23 Message-ID: #1/1 X-Deja-AN: 374199821 Sender: news@inmet.camb.inmet.com (USENET news) X-Nntp-Posting-Host: houdini.camb.inmet.com References: <35b58fd0.21988014@SantaClara01.news.InterNex.Net> Organization: Intermetrics, Inc. Newsgroups: comp.lang.ada Date: 1998-07-23T00:00:00+00:00 List-Id: Tom Moran (tmoran@bix.com) wrote: : ... but I wonder : if I'm just very lucky, or if most compilers take the allowance of : C.7.1(21) and allow 'caller to return a task_id of the environment : task, and if is_callable on the environment task becomes false when it : reaches the end of the main program and before its dependent tasks : have terminated and library level controlled objects have finalized. The environment task is a task, so 'Caller, Ada.Task_Identification.Current_Task, etc., all need to work on it. There is also nothing that disallows Is_Callable(env-task-id), so calling it should be "safe." However, it is pretty easy to imagine that the mechanism for waiting for library-level tasks follows a different path in the run-time system than that used when exiting an "explicit" task body, so it seems possible that Is_Callable(env-task) might remain true indefinitely (or perhaps false indefinitely). Clearly, you will need to test this out on each Ada run-time you intend to use. -- -Tucker Taft stt@inmet.com http://www.inmet.com/~stt/ Intermetrics, Inc. Burlington, MA USA