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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,3a414836333dfef7 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-01-04 16:43:22 PST Path: archiver1.google.com!news1.google.com!postnews1.google.com!not-for-mail From: dewar@gnat.com (Robert Dewar) Newsgroups: comp.lang.ada Subject: Re: Elaboration in GNAT Date: 4 Jan 2002 16:43:22 -0800 Organization: http://groups.google.com/ Message-ID: <5ee5b646.0201041643.60ba6972@posting.google.com> References: <1006952193.650930@edh3> <5ee5b646.0111281125.7e9fbca3@posting.google.com> <1010151875.216658@edh3> NNTP-Posting-Host: 205.232.38.14 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1010191402 3844 127.0.0.1 (5 Jan 2002 00:43:22 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 5 Jan 2002 00:43:22 GMT Xref: archiver1.google.com comp.lang.ada:18572 Date: 2002-01-05T00:43:22+00:00 List-Id: "Matthew Heaney" wrote in message news:... > The one time you cannot use a categorization pragma (say, > Elaborate_Body) is > when a package withs its own children, which means a > client will have to use > pragma Elaborate_All (if it needs to call operations in > that package during > its own elaboration). I find the above incomprehensible. The normal case in which you cannot use Elaborate_Body is when you have mutually dependent packages, a common situation. It is simply horrible to prohibit this common and perfectly reasonable situation (the alternative is being forced to aggregate packages which can perfectly well be separate).