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,c1131ea1fcd630a
X-Google-Attributes: gid103376,public
From: mfb@mbunix.mitre.org (Michael F Brenner)
Subject: Re: To Initialise or not
Date: 1996/05/02
Message-ID: <4masvn$1ai@linus.mitre.org>#1/1
X-Deja-AN: 152628850
references: <318508FE.204B@sanders.lockheed.com> <Dqq1F9.CK3@thomsoft.com>
 <318792E8.28CC1042@escmail.orl.mmc.com> <Dqqws5.Dvr@world.std.com>
organization: The MITRE Corporation, Bedford Mass.
newsgroups: comp.lang.ada
Date: 1996-05-02T00:00:00+00:00
List-Id: <comp.lang.ada>


I disagree that the compiler can "easily" detect uninitialized variables,
or detect them at all. It is not possible to write a compiler that will
detect the class of variables that are not initialized to a correct 
value in the variables range (that is, all uninitialized variables and
only unitialized variables), in a finite amount of time.
Mike Brenner <mikeb@mitre.org>