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-Thread: 103376,ebfd1d7c60facfc5 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local1.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail NNTP-Posting-Date: Mon, 20 Sep 2004 16:18:55 -0500 From: "Randy Brukardt" Newsgroups: comp.lang.ada References: <414eee7d@dnews.tpgi.com.au><414efb5b$1_1@baen1673807.greenlnk.net> <87oek027dd.fsf@deneb.enyo.de> Subject: Re: elaboration circularity detected problem, How to fix? Date: Mon, 20 Sep 2004 16:19:50 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Message-ID: NNTP-Posting-Host: 64.32.209.38 X-Trace: sv3-fY715f4r2ZQ/t0pCsZdMuBI5uEZDXIW+L0L61NOwjACu8IET7e8/2FMC9rgU0lVmxJM9IC3ql2RnGxu!+iAR83VO5JhNlIvi3lwK3CUy+bVWPPUPS7DcwDcRS1izvbdLhO5rC+HoTy7az4uXPYNQbfh7mZqe X-Complaints-To: abuse@megapath.net X-DMCA-Complaints-To: abuse@megapath.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.13 Xref: g2news1.google.com comp.lang.ada:3876 Date: 2004-09-20T16:19:50-05:00 List-Id: "Florian Weimer" wrote in message news:87oek027dd.fsf@deneb.enyo.de... ... > > try building using the " -gnatE " option. > > Dynamic elaboration checks are never the best solution. If the > elaboration order can't be determined at compile-time, there is some > significant design problem in the code. I'd disagree with that. We had problems with static elaboration checks in Claw, and the design of Claw is great. :-) :-) As I recall, the problems had to do with operator symbols that would get used in default expressions before the package could be elaborated. We had to put in a bunch of Gnat-specific pragmas to eliminate the problems. Program_Error would never be raised at runtime, and remember that you need -gnatE to conform to the standard (dynamic elaboration checks is what the Standard requires). Still, it's probably better to reorganize the code, because otherwise, you'll forever have to tell people to use -gnatE (and that isn't fun, especially as lots of people never read the documentation...) Randy.