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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7ee10ec601726fbf X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-10-16 19:19:02 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!netnews.com!xfer02.netnews.com!newsfeed2.earthlink.net!newsfeed.earthlink.net!newsmaster1.prod.itd.earthlink.net!newsread1.prod.itd.earthlink.net.POSTED!not-for-mail Message-ID: <3BCCEA8C.D3BA1F26@acm.org> From: Jeffrey Carter X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: why not References: <3BC30674.BA88AAB6@brighton.ac.uk> <9pvv3t$ves$1@news.huji.ac.il> <3BC5D730.DA950CC7@boeing.com> <9q4pa7$1ad$1@nh.pace.co.uk> <3BC6ACC8.23EF21BC@free.fr> <3BC71F54.1FFE78FA@boeing.com> <1KGx7.26476$ev2.35117@www.newsranger.com> <3BC7AD82.2A0CCCD4@acm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 17 Oct 2001 02:19:00 GMT NNTP-Posting-Host: 158.252.129.2 X-Complaints-To: abuse@earthlink.net X-Trace: newsread1.prod.itd.earthlink.net 1003285140 158.252.129.2 (Tue, 16 Oct 2001 19:19:00 PDT) NNTP-Posting-Date: Tue, 16 Oct 2001 19:19:00 PDT Organization: EarthLink Inc. -- http://www.EarthLink.net X-Received-Date: Tue, 16 Oct 2001 19:15:20 PDT (newsmaster1.prod.itd.earthlink.net) Xref: archiver1.google.com comp.lang.ada:14771 Date: 2001-10-17T02:19:00+00:00 List-Id: Stephen Leake wrote: > > Jeffrey Carter writes: > > It is quite simple to write and use a list package that will accept an > > Element of any definite type. See, for example, > > PragmARC.List_Unbounded_Unprotected from the PragmAda Reusable > > Components. > > Yes, exactly. I was avoiding the term "definite" since it is a > "lanuage-lawyer" term. > > My packages support both definite and indefinite types; that is > harder. Accepting an indefinite Element type is not difficult, but is unlikely to result in an acceptable implementation for a bounded structure. > > Which is better for a library? Since I have never needed a structure to contain indefinite types, I would say the one that can only handle definite types. -- Jeff Carter "You couldn't catch clap in a brothel, silly English K...niggets." Monty Python & the Holy Grail