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, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e3ad0eba55db3514 X-Google-Attributes: gid103376,public From: Robert Dewar Subject: Re: task activation Date: 1999/12/06 Message-ID: <82fbr9$jqm$1@nnrp1.deja.com>#1/1 X-Deja-AN: 556944847 References: <383733d3_1@news1.prserv.net> X-Http-Proxy: 1.0 x39.deja.com:80 (Squid/1.1.22) for client 205.232.38.14 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Mon Dec 06 03:51:06 1999 GMT X-MyDeja-Info: XMYDJUIDrobert_dewar Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.04 [en] (OS/2; I) Date: 1999-12-06T00:00:00+00:00 List-Id: In article , Simon Wright wrote: > As Robert Dewar has mentioned a few times recently, library > level tasks can give you real headaches at elaboration time, > at any rate if you use GNAT's default elaboration scheme. The > style guide may need a bit of a rethink in this area (at least > to lay out the problems and options). Not such a headache, one of the following usually works fine Separate the task type declaration and task object declaration into separate units. Suppress elaboration checks in the task body if you know the body is not executed till after elaboration is complete. Use the pragma Restrictions to say that no entry calls appear in elaboraiton code. Sent via Deja.com http://www.deja.com/ Before you buy.