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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,6a11907952c890f5
X-Google-Attributes: gid103376,public
From: Tom Moran <tmoran@bix.com>
Subject: Re: Visible or hidden derivation for controlled types ?
Date: 1997/03/15
Message-ID: <332B1F05.31A7@bix.com>#1/1
X-Deja-AN: 225822820
References: <3329621A.3E9D@elca-matrix.ch>
Organization: InterNex Information Services 1-800-595-3333
Reply-To: tmoran@bix.com
Newsgroups: comp.lang.ada
Date: 1997-03-15T00:00:00+00:00
List-Id: <comp.lang.ada>


I know of at least two Ada 95 compilers that don't take
   type T is private;
   procedure Initialize(X : in out T);
   ...
private
   type T is new Ada.Finalization.Controlled ...
to mean that the Initialize specified is the Controlled Initialzie for
T. If this is wrong, I'm sure it will eventually be corrected, but in 
the meantime it's certainly safer and more likely portable to admit in
the public part that T is a controlled type.  Why would you want that
fact to be private, BTW?