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,8c87bf30faa2b6b
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: [Q] To initialise or not.
Date: 1996/04/26
Message-ID: <DqHoty.EFL@world.std.com>#1/1
X-Deja-AN: 151645179
references: <484274071wnr@diphi.demon.co.uk> <3180CF00.17D5@lmtas.lmco.com>
organization: The World Public Access UNIX, Brookline, MA
newsgroups: comp.lang.ada
Date: 1996-04-26T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <3180CF00.17D5@lmtas.lmco.com>,
Ken Garlington  <garlingtonke@lmtas.lmco.com> wrote:
>Actually, Normalize_Scalars cannot be used to ensure that objects are
>initialized before use; in fact, it definitely cannot be used to ensure
>objects have _valid_ values before use!

True, but it ensures the same sort of predictability that the "always
explicitly initialize" rule does.  Hopefully, you get a run-time error
with Normalize_Scalars.  Better than nothing ;-).

- Bob