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.1 required=5.0 tests=BAYES_20,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site rayssd.UUCP
Path: utzoo!linus!vaxine!wjh12!foxvax1!brunix!rayssd!sdl
From: sdl@rayssd.UUCP (Litvintchouk)
Newsgroups: net.lang.ada
Subject: Re: IO in generic packages
Message-ID: <113@rayssd.UUCP>
Date: Sun, 28-Aug-83 15:22:20 EDT
Article-I.D.: rayssd.113
Posted: Sun Aug 28 15:22:20 1983
Date-Received: Mon, 29-Aug-83 10:34:41 EDT
References: <2113@umcp-cs.UUCP> <112@rayssd.UUCP>
Organization: Raytheon Co., Portsmouth RI
List-Id: <comp.lang.ada>

By the way, I forgot to ask:  Why would you (or anyone
else) ever need to do i/o on variables of a generic formal
private type from inside the generic unit?   Except for
equality tests, your generic unit body can't assume anything
about the nature of the private type.  Of course, you may be
importing functions defined on that type as well to be used in
the generic unit, but to check their behavior you should put
i/o statements in THEIR bodies (which are defined outside
the generic unit).