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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,1a4156f047b063f X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news4.google.com!proxad.net!feeder1-2.proxad.net!news.in2p3.fr!in2p3.fr!kanaga.switch.ch!switch.ch!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: Forcing Exception Handling Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH References: <02901b13-da72-48ae-9cb3-bf1a10144c44@u3g2000vbe.googlegroups.com> <4d6c07c1$0$6885$9b4e6d93@newsspool2.arcor-online.net> <195bsgigtzacu$.13u18z09ptrtw$.dlg@40tude.net> <91988389-b17a-42cb-8f5b-9b1205604b55@y3g2000vbh.googlegroups.com> Date: Tue, 1 Mar 2011 10:51:14 +0100 Message-ID: <1l5emphfkafmg$.13m9eqgey4nyu.dlg@40tude.net> NNTP-Posting-Date: 01 Mar 2011 10:51:14 CET NNTP-Posting-Host: 2d12b45a.newsspool3.arcor-online.net X-Trace: DXC=BlY1^NP0cKWYI9]OHn9o5^McF=Q^Z^V3X4Fo<]lROoRQ8kF On Tue, 1 Mar 2011 01:34:02 -0800 (PST), iloAda wrote: > Mmmmmm...That's what I was fearing!! > Actually the idea behind my question was that I'm working on a real > time system, and as u know, we can't afford to a let a real time > system crash because of an unhandled exception. So long it crashes in real time everything is OK! (:-)) You meant rather mission-critical system, I guess. > Since I use some other > libraries in my system (that weren't written by myself or anybody else > I know) that will raise exceptions, I wanted to be forced to handle > them. You should use some static analysis tool for that. E.g. SPARK. > exception > When others => > -- Do something that will allow the system to keep on running That is of course meaningless, because you don't know WHAT happened in order to determine the SOMETHING to be done. > have u guys done something like that before? No, because see above. The most close thing is: when Error : others => Trace ("Fatal:" & Ada.Exceptions.Exception_Information (Error)); +/- raise; -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de