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: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Uninitialized "out" parameters
Date: 1996/07/18
Message-ID: <dewar.837742895@schonberg>#1/1
X-Deja-AN: 168862296
references: <31EEACDA.64880EEB@sage.inel.gov> <4smh9i$gp5@krusty.irvine.com>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-07-18T00:00:00+00:00
List-Id: <comp.lang.ada>


Adam said

"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."

That's quite wrong, you can definitely read out parameters in Ada. (this is
a new feature, you couldn't read out parameters in Ada 83, which explains
Adam's mistake). Anyway, an Ada compiler definitely must NOT give an 
error for this program (it may give a warning).