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,e8c8d1c63ffacf0d X-Google-Attributes: gid103376,public From: Robert A Duff Subject: Re: Constraint checking of actuals passed to Attributes Date: 2000/05/09 Message-ID: #1/1 X-Deja-AN: 621320448 Sender: bobduff@world.std.com (Robert A Duff) References: <391250A8.99D1585C@hotmail.com> <39171B69.2F983487@averstar.com> <8f93lm$1es$1@nnrp1.deja.com> <8f99gf$8eo$1@nnrp1.deja.com> <8f9a87$97r$1@nnrp1.deja.com> <8f9c45$be5$1@nnrp1.deja.com> <8f9sjg$v3t$1@nnrp1.deja.com> <8f9v2i$258$1@nnrp1.deja.com> Organization: The World Public Access UNIX, Brookline, MA Newsgroups: comp.lang.ada Date: 2000-05-09T00:00:00+00:00 List-Id: Ted Dennison writes: > I mean, what's the difference *how* the garbage was achieved? The affect > of trying to work with it is what matters, and there is no difference I > can see there (no matter how you want to word the standard). The discussion was about uninitialized variables, completely within the Ada world. That's a big difference from "values" produced by Unchecked_Conversion or interface to some other language. The latter are isolated in specific modules (one hopes), whereas variable declarations appear all over the place. It's fine with me if one has to inspect the interfaced values carefully, or call 'Valid or some such, but it shouldn't cause havoc to simply forget to initialize a variable in plain vanilla Ada code. - Bob