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,baa6871d466e5af9
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: AQ&S Guidance on pragma Elaborate_Body
Date: 1997/04/23
Message-ID: <E9415t.8z9@world.std.com>#1/1
X-Deja-AN: 236974639
References: <528878564wnr@diphi.demon.co.uk>
 <mheaney-ya023680002204970735480001@news.ni.net> <E91yH8.36E@world.std.com>
 <mheaney-ya023680002204972039270001@news.ni.net>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.lang.ada
Date: 1997-04-23T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <mheaney-ya023680002204972039270001@news.ni.net>,
Matthew Heaney <mheaney@ni.net> wrote:
>  Why You Need Pragma Elaborate_All And Not Just Elaborate
>
>o  An instantiation of a generic inside another generic (package) isn't
>really elaborated until the elaboration of the instantiation of the
>enclosing generic.  So that's why we need pragma Elaborate_All and not just
>pragma Elaborate.
>
>o  If you call a subprogram of a package you with'd during your
>elaboration, you need to pragma Elaborate_All, to cover elaboration of
>library units in the called subprogram.

Right.

In practice, this leads to the simple rule: Always use Elaborate_All
instead of Elaborate, except when you can't.  "When you can't" means
there's some sort of mutual recursion going on, and you have to use
Elaborate instead.

- Bob