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=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,19c470088f7334d3,start X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.224.189.78 with SMTP id dd14mr12001688qab.0.1360008272910; Mon, 04 Feb 2013 12:04:32 -0800 (PST) X-Received: by 10.49.4.231 with SMTP id n7mr1883171qen.34.1360008272874; Mon, 04 Feb 2013 12:04:32 -0800 (PST) Path: k2ni6832qap.0!nntp.google.com!p13no10866165qai.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 4 Feb 2013 12:04:32 -0800 (PST) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=75.48.217.169; posting-account=-WG8VgoAAAAlWewKFi0J7zSTMYXZyyK3 NNTP-Posting-Host: 75.48.217.169 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <996a2b43-d409-4762-b795-85831b62419b@googlegroups.com> Subject: Psuedo-Dynamic memory with Spark? From: Diogenes Injection-Date: Mon, 04 Feb 2013 20:04:32 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2013-02-04T12:04:32-08:00 List-Id: Normally Spark does not allow Dynamic Memory allocation during program exec= ution. However is there a way to allow a Spark program to allocate memory a= t program elaboration? i.e. At program the program/process/partition boot s= equence? Since each each instance of the program might have different memor= y requirements. The memory requirements would remain static during the execution of the mai= n program, I just need to have the ability to allocate different amounts of= memory during program initialization. Also, I was thinking that it might be useful if Spark, by default, barred d= ynamic memory allocation, except in cases where the programmer called Ada.S= torage_Pools explicitly. And then only allowed it at the library level, and= only with the packages that explicitly "with"ed the Storage_Pool implement= ation. Yes, no? Diogenes