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,803df5f3f60558d5
X-Google-Attributes: gid103376,public
From: Dale Stanbrough <dale@goanna.cs.rmit.edu.au>
Subject: Re: Uninitialized "out" parameters
Date: 1996/07/19
Message-ID: <4smmhe$9cs@goanna.cs.rmit.edu.au>#1/1
X-Deja-AN: 169583383
distribution: world
references: <4smh9i$gp5@krusty.irvine.com>
content-type: text/plain; charset=ISO-8859-1
organization: RMIT, Melbourne, Australia
mime-version: 1.0
newsgroups: comp.lang.ada
Date: 1996-07-19T00:00:00+00:00
List-Id: <comp.lang.ada>


Adam Beneschan writes:
"Well, you can't read an "out" parameter at all, so it's illegal to use
 "op" in the right-hand side of your assignment.  So the compiler
 should give you an error.  Also, in Ada83, you'll get an error because
 I needs to be declared before the code for SubP appears.
 
 If you change op to an "in out" parameter, you'll be reading an
 uninitialized variable, but typically neither the compiler nor the
 runtime will complain."
 
 
Ada95 does allow you to read out parameters. The code written simply
uses an uninitialized variable, and I would imagine it would be declared
erroneous by the LRM.

Dale