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,16e3a8dd4f3ab3f3
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Elaboration order
Date: 1996/03/20
Message-ID: <dewar.827341538@schonberg>#1/1
X-Deja-AN: 143414644
references: <314701A1.469D@lfwc.lockheed.com>
 <314D2E1C.5C72@lfwc.lockheed.com> <4in4am$klb@watnews1.watson.ibm.com>
 <4inpiv$alk@cliffy.lfwc.lockheed.com> <DoJqBL.362@world.std.com>
 <4ip58c$gqo@cliffy.lfwc.lockheed.com>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-03-20T00:00:00+00:00
List-Id: <comp.lang.ada>

"Thanks for the input, but that doesn't help me quantify the risk. Scanning
the machine code for  a complex application (assume over 200 packages), looking
for a class of error which neither of us has seen, does not give me any
confidence that we would catch the error if it did show up. Some sort
of automated verification is a possibility, but I need a better understanding
of the risk before I propose a new tool. And getting a grasp on the risk
was the intent of my original post."

To minimize this risk, minimize or even eliminate ALL elaboration (it is
not out of the question to rquire pragma Preelaborate in all units for
a safety-critical application).