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: Robert A Duff <bobduff@world.std.com>
Subject: Re: task activation
Date: 1999/12/06
Message-ID: <wccemd0m5ez.fsf@world.std.com>#1/1
X-Deja-AN: 557300300
Sender: bobduff@world.std.com (Robert A Duff)
References: <383733d3_1@news1.prserv.net> <wccg0xyxw9v.fsf@world.std.com>
 <Pine.A41.3.96-heb-2.07.991202095535.101932A-100000@pluto.mscc.huji.ac.il>
 <x7vpuwnll5s.fsf@pogner.demon.co.uk> <82fbr9$jqm$1@nnrp1.deja.com>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.lang.ada
Date: 1999-12-06T00:00:00+00:00
List-Id: <comp.lang.ada>

Robert Dewar <robert_dewar@my-deja.com> writes:

> Suppress elaboration checks in the task body if you know the
> body is not executed till after elaboration is complete.

I don't understand this one.  What effect does this have on the static
elab method?  I thought that if you use the static elab method, you
wouldn't get any checks at all, so what's the point of suppressing them?

- Bob