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,e3ad0eba55db3514 X-Google-Attributes: gid103376,public From: Simon Wright Subject: Re: task activation Date: 1999/12/03 Message-ID: #1/1 X-Deja-AN: 556608811 X-NNTP-Posting-Host: pogner.demon.co.uk:158.152.70.98 References: <383733d3_1@news1.prserv.net> X-Trace: news.demon.co.uk 944331303 nnrp-01:14506 NO-IDENT pogner.demon.co.uk:158.152.70.98 Organization: At Home Newsgroups: comp.lang.ada X-Complaints-To: abuse@demon.net Date: 1999-12-03T00:00:00+00:00 List-Id: Ehud Lamm writes: > On Mon, 22 Nov 1999, Robert A Duff wrote: > > |Another way to control the timing of activation is to put the task in > |the heap -- then, an allocator causes the activation, and you can put > |that allocator whereever you like. > > Just a reminder, that though sometimes useful, this is discouraged by the > style guide. 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). -- Simon Wright Work Email: simon.j.wright@gecm.com Alenia Marconi Systems Voice: +44(0)2392-701778 Integrated Systems Division FAX: +44(0)2392-701800