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,FREEMAIL_FROM, INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,28b389d4503cb555 X-Google-Attributes: gid103376,public From: Mats Weber Subject: Re: generic package dilemma Date: 1999/11/19 Message-ID: <3835CF7A.5604C6A3@mail.com>#1/1 X-Deja-AN: 550974280 Content-Transfer-Encoding: 7bit References: <80u48b$ghr$1@bunyip.cc.uq.edu.au> <3832e27f_1@news1.prserv.net> <3832E75D.5B1BA719@mail.com> <383319e8_4@news1.prserv.net> <3833F615.5AD7166C@mail.com> <383442e1_1@news1.prserv.net> <383510EA.9DFEE8B6@mail.com> <383569db_2@news1.prserv.net> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: VTX Services SA Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-11-19T00:00:00+00:00 List-Id: Matthew Heaney wrote: > I just assumed that whenever you instantiate a package (inside another > package), that you have to pragma Elaborate_All the generic unit. > > But you seem to advocate only a conditional application of this > guideline. When specifically do you recommend using Elaborate_All, > versus not needing to bother? Actually, I have used pragma Elaborate(_All) maybe three times since 1983. I have always let the compiler figure out an elaboration order, which turned out to be just fine in almost all cases with DEC Ada, Verdix and GNAT. I know this approach is not striclty portable, but I don't care and I still think that some minimal automatic elaboration order generation should be in the language standard (see my thesis).