Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!ucbvax!info-vax
From: ESC1111@DDAESA10.BITNET
Newsgroups: mod.computers.vax
Subject: VMC Condition handlers
Message-ID: <8602221014.AA09171@ucbvax.berkeley.edu>
Date: Sat, 22-Feb-86 05:14:50 EST
Article-I.D.: ucbvax.8602221014.AA09171
Posted: Sat Feb 22 05:14:50 1986
Date-Received: Sun, 23-Feb-86 02:15:02 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 29
Approved: info-vax@sri-kl.arpa

VMS Condition Handlers - do they work?

We are just starting to design a moderately complex
interactive cum real-time application to run under VMS 4.2, to
be written in FORTRAN (why FORTRAN? - ask me another!).I
have been reading all sorts of VMS books and am very happy
to discover the Condition Handler support - it seems to me
that this should greatly help the production of reasonably
robust software.

The only problem is that one of my colleagues was told (in a
previous project) to avoid condition handlers like the
plague 'cos they didn't work safely. He's not sure if this
applied only to their use in the particular language (CORAL)
and its run-time library or if this was a general caveat.

Anyone got any bad (or good come to that) experiences with
condition handlers, especially in combination with FORTRAN?
Do you think they are a help or a hindrance to producing
good systems?

------------ standard denial of everything ------
any views expressed are purely my own and may not reflect those
of my employer - the European Space Agency

         N. Head,                 ESC1111@DDAESA10, ESC1111%ESOC.BITNET
         RobertBoschstr. 5
         6100 Darmstadt
         Federal Rep. Germany