Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!udel!haven!adm!news
From: guillory@storm.dnet.nasa.gov (Anthony R. Guillory (904))
Newsgroups: comp.lang.pascal
Subject: RE: Re: Re: HANDLING FLOATING POINT OVERFLOW ERROR IN TP
Message-ID: <25374@adm.brl.mil>
Date: 3 Jan 91 12:53:40 GMT
Sender: news@adm.brl.mil
Lines: 48


Here's a small excerpt from an run-time error handling routine I wrote. 
I don't know if this will help, but here it is.


{$F+} Procedure RuntimeErrorHandler; {$F-}

Begin

If (ExitCode <> 0) AND (ErrorAddr <> NIL)
Then Begin
 
        [Print "My" Error Message]

        ErrorAddr := NIL; { Cancel Runtime Error }
        ExitCode := 0;
     End { Then };

ExitProc := SavedExitProc;

End { RuntimeErrorHandler };

Begin

   SavedExitProc := ExitProc;      { Save ExitProc pointer }
   ExitProc := @RuntimeErrorHandler;

End. { ExitProc }




_______________________________________________________________________________
 
Anthony R. Guillory
 
INTERNET:    Guillory@Storm.dnet.nasa.gov
UUCP:        {ames,east,decwrl,ucbvax,uunet}!storm.dnet.nasa.gov!guillory
CompuServe:  73427,2515
GEnie:       A.GUILLORY
FidoNet:     Anthony Guillory @ 1:3605/46
DECNET/SPAN: STORM::GUILLORY  or  723::GUILLORY

 o If practice makes perfect, and nobody's perfect, why practice?
 o The solution of this problem is trival and is left as an exercise for
   the reader.
 o Recursive,adj.; see recursive.
_______________________________________________________________________________