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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,419864ed91cc937d
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!proxad.net!feeder1-2.proxad.net!newsfeed.straub-nv.de!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Natasha Kerensikova <lithiumcat@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: heap size exceeded for large matrices
Date: Mon, 30 Aug 2010 09:55:48 +0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <slrni7n014.dki.lithiumcat@sigil.instinctive.eu>
References: 
 <14007b1b-c290-4c73-a0ec-d3c5195b83d4@t20g2000yqa.googlegroups.com>
 <4c7a360b$0$10227$ba4acef3@reader.news.orange.fr>
 <g9tk76ljou9a3in805jes6n6pg4oqtcna6@4ax.com>
 <340c87af-1f15-4590-baa9-ec7e864b7048@l20g2000yqm.googlegroups.com>
 <4c7ada3c$0$2372$4d3efbfe@news.sover.net>
 <slrni7moa0.dki.lithiumcat@sigil.instinctive.eu>
 <15vm76lljrgcsrco2l1139s9ah3dsp07jm@4ax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 30 Aug 2010 09:55:48 +0000 (UTC)
Injection-Info: mx01.eternal-september.org;
 posting-host="Mda950WjNwNLAFOE7yJXQw";
	logging-data="25976"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/ckF7YLHdJWZLM4TIqEL0G"
User-Agent: slrn/0.9.9p1 (FreeBSD)
Cancel-Lock: sha1:cTObH4ABrLfX81q55vHnVKrWnRU=
Xref: g2news1.google.com comp.lang.ada:13844
Date: 2010-08-30T09:55:48+00:00
List-Id: <comp.lang.ada>

On 2010-08-30, Brian Drummond <brian_drummond@btconnect.com> wrote:
> On Mon, 30 Aug 2010 07:44:00 +0000 (UTC), Natasha Kerensikova
><lithiumcat@gmail.com> wrote:
>
>>On 2010-08-29, Peter C. Chapin <chapinp@acm.org> wrote:
>>> Be aware that you may now have to explicitly deallocate the array at
>>> some point. How necessary that is will depend on your program and some
>>> other factors. It's something to keep in mind.
>>
>>Are there some facilities like C++'s auto_ptr (i.e. containers that
>>behaves like pointers but with a reference counter, so that when the
>>last container is finalized the pointed data is release automatially)?
>>I haven't seen any, have I missed it?
>
> Have you looked at controlled types?

Yes, that's why I said such an auto_ptr would be very easily
implemented, with controlled types and generics. But the auto_ptr
itself, as far as I know, does not exist (yet). There should probably a
reason, shoudn't it?


Natasha