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,e723b158fb4ad12e
X-Google-Attributes: gid103376,public
From: Simon Wright <simon@pogner.demon.co.uk>
Subject: Re: Initialized global data
Date: 1998/05/08
Message-ID: <x7vhg30zu85.fsf@pogner.demon.co.uk>#1/1
X-Deja-AN: 351446684
X-NNTP-Posting-Host: pogner.demon.co.uk:158.152.70.98
References: <6iosc2$3mp@bgtnsc01.worldnet.att.net>
 <199805061414.QAA14832@basement.replay.com>
X-Complaints-To: abuse@demon.net
X-Trace: news.demon.co.uk 894640365 nnrp-05:1129 NO-IDENT
 pogner.demon.co.uk:158.152.70.98
Organization: At Home
Newsgroups: comp.lang.ada
Date: 1998-05-08T00:00:00+00:00
List-Id: <comp.lang.ada>


nobody@REPLAY.COM (Anonymous) writes:
[...]
> Or you can use an uninitialized "variable" (that doesn't) at a specified
> address:
> 
> X : T;
> for X'Address use A; -- Ada 83: "for X use at A;"

I'm not sure of chapter-and-verse, but I believe that a compiler is
allowed to initialize X here under some circumstances; which wouldn't
be what you wanted!

The specific case where this happened to us was when T happened to be
a packed array of bits. We were assured by our support that it was OK
for their compiler to initialize all the bits to 0, I was dubious
about this! (and I can't seem to recreate the situation in the latest
release ..)