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,deeb88b0e7eede4f
X-Google-Attributes: gid103376,public
From: Steve Howard <howard@mtm.syr.ge.com>
Subject: Re: Help with Exceptions!
Date: 1996/05/07
Message-ID: <318F353D.4531@mtm.syr.ge.com>#1/1
X-Deja-AN: 153481210
references: <4mmimq$s4r@hatathli.csulb.edu>
content-type: text/plain; charset=us-ascii
organization: Lockheed Martin Ocean, Radar & Sensor Systems - Syracuse
mime-version: 1.0
newsgroups: comp.lang.ada
x-mailer: Mozilla 2.0 (WinNT; I)
Date: 1996-05-07T00:00:00+00:00
List-Id: <comp.lang.ada>


Robert Gelb wrote:

> My question is this: when I catch an error with the
> exception, how can I go back to statement where the error occured (or the
> statement next to it)?

Unfortunately perhaps, but you can't go back... the exception 
terminates the current frame. The best that your exception 
handler can do is recover from the error by resetting to some 
default conditions, or re-raise the exception, as well as 
possibly logging the error somehow.

-- 
E. Steve Howard                | Lockheed Martin
                               | Ocean, Radar, & Sensor Systems        
mailto:howard@mtm.syr.ge.com   | Syracuse, NY