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=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d02eb5c33ac65d9
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-03-09 17:45:02 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeed.berkeley.edu!ucberkeley!hammer.uoregon.edu!arclight.uoregon.edu!wn13feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!sccrnsc03.POSTED!not-for-mail
From: Mark Biggar <mark.a.biggar@attbi.com>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US;
 rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Array and memory usage
References: <slrnb6m8mg.15o.randhol+news@kiuk0152.chembio.ntnu.no>
 <2397C8D4BA396B7A.ADB0E590CE8E5EAE.1C7AEC9AFCA7BE12@lp.airnews.net>
 <slrnb6mbnv.8a1.randhol+news@kiuk0152.chembio.ntnu.no>
 <b4fftn$o3b$1@slb2.atl.mindspring.net>
In-Reply-To: <b4fftn$o3b$1@slb2.atl.mindspring.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <x6Saa.25310$eG2.4454@sccrnsc03>
NNTP-Posting-Host: 12.235.88.213
X-Complaints-To: abuse@attbi.com
X-Trace: sccrnsc03 1047260701 12.235.88.213 (Mon, 10 Mar 2003 01:45:01 GMT)
NNTP-Posting-Date: Mon, 10 Mar 2003 01:45:01 GMT
Organization: AT&T Broadband
Date: Mon, 10 Mar 2003 01:45:01 GMT
Xref: archiver1.google.com comp.lang.ada:35106
Date: 2003-03-10T01:45:01+00:00
List-Id: <comp.lang.ada>

Marin David Condic wrote:
> Note that it is *probably* generating code that will initialize the objects
> as they are created. It is probably also not the most efficient way that the
> initialization could be done, either. I've seen major problems with embedded
> code where we've wanted to initialize global RAM data and couldn't get
> static initialization of it using the usual Ada mechanisms. I've also seen
> where initialization of the type would generate code to initialize each
> field of the record with function calls but initialization of the object
> with an aggregate would result in a simple memory move of the whole thing.
> 
> If you care about code size and efficiency, you can find a number of
> "surprises" and "gotchas" with Ada.

Shouldn't the preelaborate pragma help with this problem?  Otherwise
this is obviously a "quality or implementation" issue.


-- 
Mark Biggar
mark.a.biggar@attbi.com