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: 103376,8ecbc35ea893182f
X-Google-Attributes: gid103376,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news2.google.com!news1.google.com!news.glorb.com!peer1.news.newnet.co.uk!194.159.246.34.MISMATCH!peer-uk.news.demon.net!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail
From: Simon Wright <simon.j.wright@mac.com>
Newsgroups: comp.lang.ada
Subject: Re: Interfacing to C: big structures
Date: Wed, 27 Feb 2008 20:37:58 +0000
Organization: Pushface
Message-ID: <m23are3zkp.fsf@mac.com>
References: 
 <c48dc7da-6f04-4f0f-9a8f-e0acc371ee3c@o10g2000hsf.googlegroups.com>
 <62idb0F23ddfnU1@mid.individual.net>
 <56a177e4-506f-4bc8-a531-7f2dd15d50c8@i7g2000prf.googlegroups.com>
 <m27igr4i0b.fsf@mac.com>
 <21af9a6a-d522-4ba5-9d67-68eace9cd1b1@n77g2000hse.googlegroups.com>
NNTP-Posting-Host: pogner.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.demon.co.uk 1204144678 27054 62.49.19.209 (27 Feb 2008 20:37:58
 GMT)
X-Complaints-To: abuse@demon.net
NNTP-Posting-Date: Wed, 27 Feb 2008 20:37:58 +0000 (UTC)
Cancel-Lock: sha1:w6/gYFArzj6GHGaVNzdhoPvqzvo=
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (darwin)
Xref: g2news1.google.com comp.lang.ada:20131
Date: 2008-02-27T20:37:58+00:00
List-Id: <comp.lang.ada>

Adam Beneschan <adam@irvine.com> writes:

> Isn't that part of "runtime"?  I'm not sure I get your point.

Um, thinking about it from that point of view, you are all quite
right, of course.

When I've had/heard of restrictions, it's only ever been in
environments where it was the use of the word 'new' that was frowned
upon rather than the actual allocation of memory after execution
startup. Even there it seems reasonable to fight for the right to do
explicit one-off startup allocations - no risk of fragmentation if the
memory's never freed.