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,865e31ac5a1b553a X-Google-Attributes: gid103376,public From: "Steve Doiel" Subject: GNAT -vs- ObjectAda (was Re: where is the faq) Date: 1999/07/17 Message-ID: <3790b774.0@news.pacifier.com>#1/1 X-Deja-AN: 502138980 References: <7mneah$g5j$1@nnrp1.deja.com> X-Trace: 17 Jul 1999 10:03:48 PST, 216.65.140.220 Newsgroups: comp.lang.ada X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Date: 1999-07-17T00:00:00+00:00 List-Id: tmoran@bix.com wrote in message ... >>> Failing that, what is the best Win NT compiler? >> >>That depends on what your critera are. > Note also that Aonix (among others) gives you a complete walk-back >in ada.exceptions.exception_information and also in case of an >unhandled exception. With Gnat you'll get "Constraint Error" or such >as your only clue about where the problem might lie. So, unless you >write perfect code every time, the first time, you'll *always* need >to run Gnat exe's under the debugger. If you want similar failure >information if your program dies on a customer, you'll have to tell >him to run your program only under the debugger. This is exactly why we're using ObjectAda right now over GNAT. In our code we quietly write the exception information to a file and keep the system running. We can then correct the cause of exceptions at our leisure. I believe that GNAT would require that the program be stopped in the debugger. BTW: I have heard that in some time in the future (don't know when) similar traceback information will be available for GNAT. We have compiled and ran our code under both ObjectAda and GNAT. The code compiled under GNAT tends to run approximately 2X the speed. The GNAT debugger (GDB) also permits viewing nearly all variables, while the ObjectAda debugger is somewhat limited in this regard, which is frustrating. At some time in the not to distant future (I hope) Aonix will be releasing a new version of ObjectAda (7.2) that is supposed to fix most of their debugger woes. This release is already more than 6 months late. SteveD