Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!rex!uflorida!bernhold
From: bernhold@red8 (David E. Bernholdt)
Newsgroups: comp.lang.fortran
Subject: Error handling in large programs -- another question
Message-ID: <28791@uflorida.cis.ufl.EDU>
Date: 29 May 91 03:08:33 GMT
Article-I.D.: uflorida.28791
References: <28787@uflorida.cis.ufl.EDU>
Sender: news@uflorida.cis.ufl.EDU
Organization: Quantum Theory Project, Univ. of Florida
Lines: 29

In article <28787@uflorida.cis.ufl.EDU> I wrote:
>How do you handle errors in large (Fortran) codes?

>I'm interested in everything from the grand philosophy to the small
>details.  For example:

I thought of another question or two:

o  Do you make any attempt to deal with I/O errors beyond a
   success/failure/end-of-file level?  Portably?  Do you attempt to
   analyze the source of the error and recover (if possible) or do you
   just try to give a more informative error message?

o  Did you adopt a particular style for error messages -- like, say VMS
   or unix or something else?  Why?

o  Do you make any attempt to use existing error codes/routines -- for
   example the C-preprocessor include file /usr/include/sys/errno.h on
   unix machines, or the error handling routines in VMS?

[Sorry if the examples are VMS & unix biased -- that's what I have
experience with.  How do other systems help deal with these things?]

thanks again...
-- 
David Bernholdt			bernhold@qtp.ufl.edu
Quantum Theory Project		bernhold@ufpine.bitnet
University of Florida
Gainesville, FL  32611		904/392 6365