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,803df5f3f60558d5
X-Google-Attributes: gid103376,public
From: Peter Amey <pna@erlang.praxis.co.uk>
Subject: Re: Uninitialized "out" parameters
Date: 1996/07/19
Message-ID: <Pine.SUN.3.91.960719125808.24003L-100000@erlang.praxis.co.uk>#1/1
X-Deja-AN: 169835507
references: <31EEACDA.64880EEB@sage.inel.gov> <dewar.837740222@schonberg>
content-type: TEXT/PLAIN; charset=US-ASCII
organization: Praxis plc, U.K.
mime-version: 1.0
newsgroups: comp.lang.ada
Date: 1996-07-19T00:00:00+00:00
List-Id: <comp.lang.ada>




On 18 Jul 1996, Robert Dewar wrote:
[snip]
> 
> But certainly it is impossible for a compiler to give warnings in all
> cases of uninitialized variable use.
> 

True, but high-integrity tools like the SPARK Examiner can and do; they 
also turn out to be a rich source of errors in real programs.

Peter