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=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!weretis.net!feeder4.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 21 Oct 2018 16:35:09 -0500
Newsgroups: comp.lang.ada
Subject: Storage_Size in a Simple Program
From: csampson@inetworld.net (Charles H. Sampson)
Date: Sun, 21 Oct 2018 14:35:09 -0700
Message-ID: <1nx0yp3.x6ss3k18nq71lN%csampson@inetworld.net>
User-Agent: MacSOUP/2.8.5 (ea919cf118) (Mac OS 10.12.6)
X-Usenet-Provider: http://www.giganews.com
X-Trace: 
 sv3-tXsWnvT0z6FyKtHASgzRPS+zzTdF03qMROYChgcLSWfBK3QrtE9K0fxfkRJWdIsBwKcr0RJ1t2XpFf2!Qu8cU9RnJedUc7pwyCew5EjcB6PWw43dsPmzYitx9VkCdmEvkHKtONORJ8cDr8gmNsZ7BO95C8o=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.40
X-Original-Bytes: 1871
X-Received-Bytes: 2083
X-Received-Body-CRC: 3254537323
Xref: reader02.eternal-september.org comp.lang.ada:54685
Date: 2018-10-21T14:35:09-07:00
List-Id: <comp.lang.ada>

I've got a conceptually simple program that uses a lot of memory. It is
highly recursive (using a lot of stack) and also puts a lot of stuff on
the heap. Is there any way to specify that a lot of memory is needed
other than pragma Storage_Size?

As it is, I have three totally artificial tasks hidden in packages. The
packages' entry routines are simply pass-throughs to their embedded
task's entries. There are no concurrency issues because the simple
program is single-threaded at heart.

Is that it? That's a lot of baggage just to give permission to use more
memory, particularly when there's a lot of memory lying around now.

Thanks.

Charlie
-- 
Nobody in this country got rich on his own.  You built a factory--good.
But you moved your goods on roads we all paid for.  You hired workers we
all paid to educate. So keep a big hunk of the money from your factory.
But take a hunk and pay it forward.  Elizabeth Warren (paraphrased)