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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.50.59.244 with SMTP id c20mr44795379igr.7.1431636535031;
        Thu, 14 May 2015 13:48:55 -0700 (PDT)
X-Received: by 10.140.98.175 with SMTP id o44mr119859qge.33.1431636535003;
 Thu, 14 May 2015 13:48:55 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!j8no1018898igd.0!news-out.google.com!k20ni9436qgd.0!nntp.google.com!z60no350799qgd.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 14 May 2015 13:48:54 -0700 (PDT)
In-Reply-To: <mj0sth$pim$1@loke.gir.dk>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=108.44.154.41;
 posting-account=vk6_JwoAAABkMyHO1YfdP69Hm3CpbdGR
NNTP-Posting-Host: 108.44.154.41
References: <830c0323-a06c-4884-9214-89f3ee6f17b5@googlegroups.com>
 <mitsgs$1b2$1@loke.gir.dk>
 <783ee7a2-e831-4e64-b736-abab0c7d71b7@googlegroups.com>
 <mj0sth$pim$1@loke.gir.dk>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <779e3742-327f-43de-88a3-45bac9c63d73@googlegroups.com>
Subject: Re: Incomplete types used with generics
From: Jeremiah <jeremiah.breeden@gmail.com>
Injection-Date: Thu, 14 May 2015 20:48:55 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Xref: news.eternal-september.org comp.lang.ada:25881
Date: 2015-05-14T13:48:54-07:00
List-Id: <comp.lang.ada>

On Wednesday, May 13, 2015 at 9:14:27 PM UTC-4, Randy Brukardt wrote:
> For Ada before Ada 2012, formal "limited private" was the most general th=
ing=20
> available for a generic (thus the use in books and the like), but formal=
=20
> incomplete types are more general than that. Of course, they can only be=
=20
> used like an incomplete type, and that is very limiting. It's not yet cle=
ar=20
> that much beyond signature packages can be created with them.
>=20
>                                            Randy.

That definitely makes sense.  When I moved from my simple example (modified=
 to use actual incomplete types) to something I had that was more complex I=
 already saw that in action.  I had a method that was used to deallocate th=
e access type under certain conditions, which required the complete type fo=
r Unchecked_Deallocation.  I remodeled the generic package to account for t=
hat a different way.  Luckily that was my only thing that tried to improper=
ly use the incomplete type.

Thanks again!