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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,3ebfb7ec7bfb06fa X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.181.11.170 with SMTP id ej10mr1830237wid.1.1360478314884; Sat, 09 Feb 2013 22:38:34 -0800 (PST) Path: g1ni2212wig.0!nntp.google.com!feeder1.cambriumusenet.nl!82.197.223.103.MISMATCH!feeder3.cambriumusenet.nl!feed.tweaknews.nl!194.109.133.81.MISMATCH!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!newspeer1.nac.net!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newsgate.cuhk.edu.hk!news.glorb.com!feeder.erje.net!eu.feeder.erje.net!news2.arglkargh.de!news.mixmin.net!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Passing indefinite types Date: Sun, 3 Feb 2013 09:07:27 +0100 Organization: cbb software GmbH Message-ID: <12f0uuiyq6eez.1pibxapmoi0y6.dlg@40tude.net> References: <5262a822-409a-4c79-a842-0e716527cb70@googlegroups.com> <4b47f227-4f52-49b3-b9bf-53a6d4f60263@googlegroups.com> Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: cDN0fd8KlIeJLyErIrSf0A.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Date: 2013-02-03T09:07:27+01:00 List-Id: On Sat, 2 Feb 2013 16:27:32 -0800 (PST), sbelmont700@gmail.com wrote: > On Saturday, February 2, 2013 4:31:06 PM UTC-5, Jeffrey Carter wrote: >> >> How about an indefinite container? > > I had considered it, but that only works for non-limited types, and, ultimately, uses the heap. A custom storage pool then? Sometimes I am using stack or pool mark-and-release pools. That would mean access types of course. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de