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, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,67b6ac0b061212bf X-Google-Attributes: gid103376,public From: Robert Dewar Subject: Re: GNAT Problem with variable length Arrays Date: 2000/03/22 Message-ID: <8bas7v$5nd$1@nnrp1.deja.com>#1/1 X-Deja-AN: 600896103 References: <8b9v4e$cve1@dsit03.atlas.de> X-Http-Proxy: 1.0 x36.deja.com:80 (Squid/1.1.22) for client 205.232.38.14 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Wed Mar 22 16:27:02 2000 GMT X-MyDeja-Info: XMYDJUIDrobert_dewar Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.61 [en] (OS/2; I) Date: 2000-03-22T00:00:00+00:00 List-Id: In article , Philippe Waroquiers wrote: > > I encountered once a similar problem (compilation did not stop). > > After some time, I thought to use the switch -gnate -gnatf > documented in the user's guide section '20.9 Abnormal Termination'. > The errors are then output immediately (even if the compilation > still does not stop). > > A suggestion was given to ACT to slightly modify this section and > section title in order to suggest that these switches are also useful > in case gnat does not terminate :). Note that it is NOT a good idea to routinely use -gnate, and in fact we may move this to a debugging switch. Why? because it disconnects a lot of useful error handling circuitry (GNAT needs all the error messages at hand to massage them before outputting them, if you force output as you go along, you remove this possibility), but it is indeed useful in the occasional cases where the compiler goes into a loop or gets a system exception (it is not useful in the case where a GNAT BUG DETECTED box is printed). Sent via Deja.com http://www.deja.com/ Before you buy.