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: "Theodore E. Dennison" <dennison@escmail.orl.mmc.com>
Subject: Re: To Initialise or not
Date: 1996/05/02
Message-ID: <3188AF51.1F1A7590@escmail.orl.mmc.com>#1/1
X-Deja-AN: 152606677
references: <318508FE.204B@sanders.lockheed.com> <Dqp3HF.12t@world.std.com>
 <Dqq1F9.CK3@thomsoft.com> <318792E8.28CC1042@escmail.orl.mmc.com>
 <Dqqws5.Dvr@world.std.com>
content-type: text/plain; charset=us-ascii
organization: Lockheed Martin Information Systems
mime-version: 1.0
newsgroups: comp.lang.ada
x-mailer: Mozilla 2.0 (X11; I; SunOS 4.1.3_U1 sun4m)
Date: 1996-05-02T00:00:00+00:00
List-Id: <comp.lang.ada>


Robert A Duff wrote:
> 
> In article <318792E8.28CC1042@escmail.orl.mmc.com>,
> Theodore E. Dennison <dennison@escmail.orl.mmc.com> wrote:
> >Yes, but I don't think any compiler COULD easily help enforce this (It
> >sounds a lot like the halting problem to me). That is what code
> >walkthroughs are for.
> 
> A compiler can *easily* detect uninitialized variables at run time.
> Yes, it's nicer to know about it at compile time, when possible, but as

Well, no. A compiler can't detect a thing at run-time. The compiler is
not even running then. It is happily asleep on the disk, dreaming
compiler dreams.

I do see what you are getting at, but I don't think adding a "dirty
bit" to every varaible is a serious consideration. (At least, the
systems programmer in me HOPES it isn't).

-- 
T.E.D.          
                |  Work - mailto:dennison@escmail.orl.mmc.com  |
                |  Home - mailto:dennison@iag.net              |
                |  URL  - http://www.iag.net/~dennison         |